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
Unique Key: trace_id
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