Table of contents
The eth_mainnet.traces Transactions can trigger smaller atomic actions that modify the internal state of an Ethereum Virtual Machine. Information about the execution of these actions is logged and can be found stored as an EVM execution trace, or just a trace. In Etherscan these are referred to as internal transactions.
Columns
| Name | Type | Description |
|---|---|---|
| id | varchar | N/A |
| block_hash | varchar | A unique identifier for that block |
| block_number | integer | The length of the blockchain in blocks |
| timestamp | integer | The block time |
| block_time | date | The time when the block was mined |
| parent_tx_hash | varchar | The unique identifier for the prior block |
| from | varchar | Address of the sender |
| to | varchar | Address of the receiver. null when its a contract creation transaction |
| input | varchar | The bytecode of the call that is made to another smart contract |
| output | varchar | The bytecode answer the smart contract that was called gives back. |
| value | varchar | The amount of [chain_gas_token] sent in this transaction |
| call_type | varchar | Can be staticcall, delegatecall or call |
| trace_id | varchar | N/A |
| gas | decimal(38,0) | Gas provided with the message call |
| gas_used | decimal(38,0) | The gas consumed by the transaction in wei |
| status | boolean | N/A |
| error | varchar | The error message the EVM throws if the execution of one of a contract's instructions fails. |
| ym | varchar | Year month |