Skip to main content

​
Table description

The starknet.calls table documents the execution trace of the transaction designated by the input hash.

​
Table Schema

ColumnTypeDescription
block_dateDATEThe date of the block containing this call (UTC)
block_timeTIMESTAMPThe timestamp of the block containing this call
block_numberBIGINTThe sequential number of the block containing this call
block_l1_da_modeVARCHARLayer 1 data availability mode (BLOB or CALLDATA)
block_l1_data_gas_price_in_friUINT256L1 data gas price in fri (STRK) for the block
block_l1_data_gas_price_in_weiUINT256L1 data gas price in wei (ETH) for the block
block_l1_gas_price_in_friUINT256L1 gas price in fri (STRK) for the block
block_l1_gas_price_in_weiUINT256L1 gas price in wei (ETH) for the block
block_l2_gas_price_in_friUINT256L2 gas price in fri (STRK) for the block
block_l2_gas_price_in_weiUINT256L2 gas price in wei (ETH) for the block
block_starknet_versionVARCHARThe Starknet protocol version of the block
transaction_indexINTEGERPosition of the parent transaction within the block
transaction_typeVARCHARType of the parent transaction (INVOKE, L1_HANDLER, DECLARE, DEPLOY_ACCOUNT, DEPLOY)
call_typeVARCHARType of function call (CALL, LIBRARY_CALL, or DELEGATE)
contextVARCHARExecution context of the call
entry_point_typeVARCHARType of entry point invoked (EXTERNAL, L1_HANDLER, CONSTRUCTOR)
execution_resources_bitwise_builtin_applicationsINTEGERNumber of bitwise builtin applications consumed
execution_resources_data_availability_l1_gasUINT256L1 gas consumed for data availability
execution_resources_data_availability_l1_data_gasUINT256L1 data gas consumed for data availability
execution_resources_data_availability_l2_gasUINT256L2 gas consumed for data availability
execution_resources_ec_op_builtin_applicationsINTEGERNumber of elliptic curve operation builtin applications consumed
execution_resources_ecdsa_builtin_applicationsINTEGERNumber of ECDSA builtin applications consumed
execution_resources_keccak_builtin_applicationsINTEGERNumber of Keccak builtin applications consumed
execution_resources_memory_holesINTEGERNumber of memory holes in the execution trace
execution_resources_pedersen_builtin_applicationsINTEGERNumber of Pedersen hash builtin applications consumed
execution_resources_poseidon_builtin_applicationsINTEGERNumber of Poseidon hash builtin applications consumed
execution_resources_range_check_builtin_applicationsINTEGERNumber of range check builtin applications consumed
execution_resources_segment_arena_builtinINTEGERNumber of segment arena builtin applications consumed
execution_resources_stepsINTEGERTotal number of Cairo VM steps executed
num_subcallsINTEGERNumber of nested sub-calls triggered by this call
block_hashVARBINARYHash of the block containing this call
block_new_rootVARBINARYNew global state root after the block
block_parent_hashVARBINARYHash of the preceding block
block_sequencer_addressVARBINARYAddress of the sequencer that produced the block
transaction_hashVARBINARYHash of the parent transaction
callstack_indexARRAY(INTEGER)Position in the call tree hierarchy
calldataARRAY(VARBINARY)Input data passed to this call
caller_addressVARBINARYAddress of the contract that initiated this call
class_hashVARBINARYClass hash of the called contract
contract_addressVARBINARYAddress of the contract being called
entry_point_selectorVARBINARYSelector identifying the function entry point
eventsARRAY(ROW(DATA ARRAY(VARCHAR), KEYS ARRAY(VARCHAR), EVENT_INDEX INTEGER))Events emitted during this call
messagesARRAY(ROW(FROM_ADDRESS VARBINARY, PAYLOAD VARBINARY, TO_ADDRESS VARBINARY, MESSAGE_INDEX INTEGER))L2-to-L1 messages sent during this call
resultVARBINARYReturn value of the call
revert_reasonVARCHARReason for call failure, if the call reverted
state_diffVARCHARJSON-encoded state changes resulting from this call
  • Prior to v3 transactions upgrade, fees are denominated in wei as users pay gas with ETH. For transactions v3 and later, fees are denominated in fri as users pay gas with STRK. Hence here you can see two gas types of gas fields, one for wei and one for fri.
  • Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The l1_da_mode property in the Starknet block header contains this information. Values possible are BLOB or CALLDATA.
  • The block_status has possible values ACCEPTED_ON_L1 or ACCEPTED_ON_L2. Read here to learn more about different transaction status.
  • The transaction_type fields denotes different types of transactions supported by Starknet. Possible values are: INVOKE, L1_HANDLER, DECLARE, DEPLOY_ACCOUNT, and DEPLOY.
  • The call_type fields denotes what type of function calls was invoked. Possible values are LIBRARY_CALL, CALL, or DELEGATE
  • ‘entry_point_type’: The type of entry point. Possible values includes - EXTERNAL, L1_HANDLER, CONSTRUCTOR

​
Table Sample