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 https://github.com/Allium-Science/allium-docs/blob/main/data-faq/traces-id-and-address.md for more information and examples.

Table Columns

Column NameDescription

transaction_hash

Unique identifier of the transaction that contains this trace.

transaction_index

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

from_address

The address of the sending party of this trace.

to_address

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

value

The amount of ether moved from the from_address to to_address.

input

The bytecode of the call that is made to another smart contract.

output

The bytecode answer the smart contract that was called gives back.

trace_type

The value of the method such as call, create, create2, suicide.

call_type

reward_type

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

gas

Gas provided with the trace call, in wei.

gas_used

The amount of gas consumed, in wei.

subtraces

Number of children traces.

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).

block_timestamp

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

block_number

The length of the chain, in blocks.

block_hash

Unique identifier of the block that includes this trace.

trace_id

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

selector

Selector of the txn.

_created_at

Timestamp of the entry creation.

_updated_at

Timestamp of the entry update.

Last updated