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
transaction_hash
Unique identifier of the transaction that contains this trace.
0x79dc5231dd97b54e464b084ea371b0af277b70d16fdf03808edd3608d90647ba
transaction_index
The position of this transaction in the block that it belongs to. The first transaction has index 0.
31
from_address
The address of the sending party of this trace.
0xe24fe20ca3e903b0e10536e2d82d0a4817046ddb
to_address
The address of the receiving party of this trace (null for contract creation).
0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d
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.
0xa9059cbb00000000000000000000000072a53cdbbcc1b9efa39c834a540550e23463aacb0000000000000000000000000000000000000000000000011503bb38b4c4ff74
selector
Selector of the txn.
0xa9059cbb
output
The bytecode answer the smart contract that was called gives back.
0x0000000000000000000000000000000000000000000000000000000000000001
trace_type
The value of the method such as call, create, create2, suicide.
call
reward_type
Populated when trace_type =reward. Possible values: block, uncle
gas
Gas provided with the trace call, in wei.
36,976
gas_used
The amount of gas consumed, in wei.
23,907
subtraces
Number of children traces.
1
trace_address
The address of the trace within the call graph. More detail to come soon.
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).
1
block_timestamp
The time when the block that contains this trace was included on the blockchain.
2022-08-08 18:47:12
block_number
The length of the chain, in blocks.
20,268,966
block_hash
Unique identifier of the block that includes this trace.
0x91a41c7246a83b0245c4fbff9667329b47518e6070d2b6a4e24bc8d3b8761d2d
trace_id
Unique identifier for this trace. Generated by combining the trace_type, transaction_hash and trace_address.
call_0x79dc5231dd97b54e464b084ea371b0af277b70d16fdf03808edd3608d90647ba_
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
