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 Traces ID and Address for more information and examples.

Table Columns

Column NameDescriptionExample

transaction_hash

Unique identifier of the transaction that contains this trace.

0xe45899a9915e2a6b8ab4c6f70a4d08a8e0bef20d0d911205fc56752783e713b6

transaction_index

The position of this transaction in the block that it belongs to. The first transaction has index 0.

0

from_address

The address of the sending party of this trace.

0x0de2ef9dd1cadd3625b7a0a3d8ee04c9d4d647e2

to_address

The address of the receiving party of this trace (null for contract creation).

0x06efdbff2a14a7c8e15944d1f4a48f9f95f663a4

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.

0xa9059cbb0000000000000000000000001ba2f3f590ce7fb62b7cf8d807fd32da576cb2ef0000000000000000000000000000000000000000000000000000000001606376

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

call_type

The type of method such as call, delegatecall, staticcall. Learn more here.

call

reward_type

Populated when trace_type =reward. Possible values: block, uncle

gas

Gas provided with the trace call, in wei.

224760

gas_used

The amount of gas consumed, in wei.

43928

subtraces

Number of children traces.

1

trace_address

The address of the trace within the call graph. More detail to come soon.

0,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

block_timestamp

The time when the block that contains this log was included on the blockchain.

2023-11-14 01:34:38+00:00

block_number

The length of the chain, in blocks.

783876

block_hash

Unique identifier of the block that includes this log.

0x065a88bfec835772bb9a3cb9bb19eafc5fbad83a56c2e0e840e99223620519bf

trace_id

Unique identifier for this trace. Generated by combining the trace_type, transaction_hash and trace_address.

call_0xe45899a9915e2a6b8ab4c6f70a4d08a8e0bef20d0d911205fc56752783e713b6_0_0

selector

Selector of the txn.

0xa9059cbb

_created_at

Timestamp of entry creation.

2023-11-14 04:46:42.330000+00:00

_updated_at

Timestamp of entry update.

2023-11-14 04:46:42.330000+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