Skip to main content
Schema: flow.core_evm Table: fact_traces Type: Base Table

​
Description

A comprehensive fact table containing execution trace data for transactions on EVM-compatible blockchains. This table provides detailed information about the internal execution of transactions, including contract calls, value transfers, and execution paths. The table supports deep transaction analysis, debugging, and understanding complex contract interactions across multiple EVM chains. Each record represents a single execution step with complete trace information and execution context.

​
Key Use Cases

  • Transaction Debugging: Understanding why transactions failed or behaved unexpectedly
  • Contract Interaction Analysis: Tracking complex multi-contract interactions and call chains
  • Value Flow Tracking: Following native token and value transfers through complex transactions
  • Gas Usage Analysis: Understanding detailed gas consumption patterns in contract execution
  • Security Analysis: Identifying potential security issues and attack patterns
  • Cross-Chain Trace Analysis: Comparing execution patterns across different EVM-compatible blockchains

​
Important Relationships

  • core_evm__fact_transactions: Links to transactions that generated these traces
  • core_evm__fact_blocks: Links to blocks containing trace data
  • core_evm__dim_contracts: Links to contract metadata for trace analysis
  • core_evm__ez_native_transfers: May link to curated native transfer events
  • core_evm__fact_event_logs: May link to events emitted during trace execution
  • core__fact_transactions: May provide comparison data with native Flow transactions

​
Commonly-used Fields

  • TRACE_INDEX: Essential for trace ordering and execution sequence analysis
  • FROM_ADDRESS/TO_ADDRESS: Critical for call flow analysis and contract interaction tracking
  • TYPE: Important for trace categorization and execution type analysis
  • VALUE: Key for value transfer tracking and economic analysis
  • GAS_USED: Critical for gas consumption analysis and optimization studies
  • TRACE_SUCCEEDED: Essential for execution success analysis and error tracking

​
Columns

Column NameData TypeDescription
BLOCK_NUMBERNUMBERAlso known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block.
BLOCK_TIMESTAMPTIMESTAMP_NTZThe date and time at which the block was produced.
TX_HASHTEXTTransaction hash is a unique 66-character identifier that is generated when a transaction is executed.
TX_POSITIONNUMBERThe position of the transaction within the block.
TRACE_INDEXNUMBERThe index of the trace within the transaction.
FROM_ADDRESSTEXTThe sending address of this transaction.
TO_ADDRESSTEXTThe receiving address of this transaction. This can be a contract address.
INPUTTEXTThe input data for this trace.
OUTPUTTEXTThe output data for this trace.
TYPETEXTThe type of internal transaction. Common trace types are CALL, DELEGATECALL, and STATICCALL.
TRACE_ADDRESSTEXTThe trace address for this trace.
SUB_TRACESNUMBERThe amount of nested sub traces for this trace.
VALUEFLOATThe value transacted in the native asset.
VALUE_PRECISE_RAWTEXTThe precise, unadjusted amount of the transaction. This is returned as a string to avoid precision loss.
VALUE_PRECISETEXTThe precise, adjusted amount of the transaction. This is returned as a string to avoid precision loss.
VALUE_HEXTEXTThe value of the transaction in hexadecimal format.
GASNUMBERThe gas supplied for this trace.
GAS_USEDNUMBERThe gas used for this trace.
ORIGIN_FROM_ADDRESSTEXTThe sending address of this trace. This is not necessarily the from address of the transaction.
ORIGIN_TO_ADDRESSTEXTThe receiving address of this trace. This is not necessarily the to address of the transaction.
ORIGIN_FUNCTION_SIGNATURETEXTThe function signature of the contract call that triggered this transaction.
TRACE_SUCCEEDEDBOOLEANThe boolean value representing if the trace succeeded.
ERROR_REASONTEXTThe reason for the trace failure, if any.
REVERT_REASONTEXTThe reason for the revert, if available.
TX_SUCCEEDEDBOOLEANWhether the transaction was successful, returned as a boolean.
FACT_TRACES_IDTEXTThe unique identifier for each row in the table.
INSERTED_TIMESTAMPTIMESTAMP_NTZThe UTC timestamp at which the row was inserted into the table.
MODIFIED_TIMESTAMPTIMESTAMP_NTZThe UTC timestamp at which the row was last modified.