Traces keep track of the actions that modify the internal state of the EVM.

Typically, trace_id for traces are unique, unless there are duplicate transactions on the blockchain.

Refer here for more information and examples.

Table Columns

Column NameDescription
transaction_hashUnique identifier of the transaction that contains this trace.
transaction_indexThe position of this transaction in the block that it belongs to. The first transaction has index 0.
from_addressThe address of the sending party of this trace.
to_addressThe address of the receiving party of this trace (null for contract creation).
valueThe amount of ether moved from the from_address to to_address.
inputThe bytecode of the call that is made to another smart contract.
outputThe bytecode answer the smart contract that was called gives back.
trace_typeThe value of the method such as call, create, create2, suicide.
call_typeThe type of method such as call, delegatecall, staticcall. Learn more here.
reward_typePopulated when trace_type =reward. Possible values: block, uncle
gasGas provided with the trace call, in wei.
gas_usedThe amount of gas consumed, in wei.
subtracesNumber of children traces.
trace_addressThe address of the trace within the call graph. More detail to come soon.
errorHuman readable developer error message. Examples: “Out of gas”, “Reverted”, “Bad instruction”, “Bad jump destination”
statusSuccess status of the trace. Either 1 (success) or 0 (failure).
block_timestampThe time when the block that contains this trace was included on the blockchain.
block_numberThe length of the chain, in blocks.
block_hashUnique identifier of the block that includes this trace.
trace_idUnique identifier for this trace. Generated by combining the trace_type, transaction_hash and trace_address.
selectorSelector of the txn.
_created_atTimestamp of the entry creation.
_updated_atTimestamp of the entry update.