Traces
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 to for more information and examples.
Table Columns
block_number
The length of the chain, in blocks.
4449503
block_timestamp
The time when the block that contains this log was included on the blockchain.
2023-09-26 00:32:33+00:00
block_hash
Unique identifier of the block that includes this log.
0x2cb1215f455ebdd7e53cc372065cf8227cd577bc36c5f6f91423b7ae68e0f0e8
transaction_hash
Unique identifier of the transaction that contains this trace.
0x7af37c45cdd68c1c878edbaaa1e0cf338b21dbc850d57d65bf946cded3f0a290
transaction_index
The position of this transaction in the block that it belongs to. The first transaction has index 0.
10
from_address
The address of the sending party of this trace.
0xffcbf84650ce02dafe96926b37a0ac5e34932fa5
to_address
The address of the receiving party of this trace (null for contract creation).
0xeb585163debb1e637c6d617de3bef99347cd75c8
value
The amount of ether moved from the from_address to to_address.
0
input
The bytecode of the call that is made to another smart contract.
0x6d5433e60000000000000000000000000000000000000000000000000000000000000b990000000000000000000000000000000000000000000000000000000000000001
selector
Selector of the txn.
0x6d5433e6
output
The bytecode answer the smart contract that was called gives back.
0x0000000000000000000000000000000000000000000000000000000000000b99
trace_type
The value of the method such as call, create, create2, suicide.
call
call_type
The type of method such as call, delegatecall, staticcall. Learn more here.
delegatecall
reward_type
Populated when trace_type =reward. Possible values: block, uncle
gas
Gas provided with the trace call, in wei.
16993195
gas_used
The amount of gas consumed, in wei.
340
subtraces
Number of children traces.
0
error
Human readable developer error message. Examples: "Out of gas", "Reverted", "Bad instruction", "Bad jump destination".
status
Success status of the trace. Either 1 (success) or 0 (failure). Error messages take precedence over trace status. Note that debug_trace methods may still return status = 1 for error traces.
1
trace_id
Unique identifier for this trace. Generated by combining the trace_type, transaction_hash and trace_address.
call_0x7af37c45cdd68c1c878edbaaa1e0cf338b21dbc850d57d65bf946cded3f0a290_105_0_0_1
trace_address
The address of the trace within the call graph. More detail to come soon.
105,0,0,1
_created_at
Timestamp of the entry creation.
2023-09-26 01:06:12+00:00
_updated_at
Timestamp of the entry update.
2023-09-26 01:06:12+00:00
Additional Info
Trace Address field different from Etherscan/Explorers
The number of traces Allium has indexed for this transaction is 12, whereas if you count the number of traces that Etherscan has on this page, you'll notice that it is 11. Etherscan has chosen to leave out certain types of traces and coupled with how trace addresses are generated, it will result in a different trace address numbering scheme.
In the example above, the trace in the example as indexed by Allium is {0,0,2,0} whereas on Etherscan/Block Explorer it's as follows:
Last updated
