| BLOCK_NUMBER | NUMBER | Sequential counter representing the position of a block in the blockchain since genesis (block 0). Key Facts: Immutable once finalized Primary ordering mechanism for blockchain data Increments by 1 for each new block Used as a proxy for time in many analyses Usage in Queries: Important: Block numbers are chain-specific. Block 15000000 on Ethereum ≠ block 15000000 on Polygon. |
| BLOCK_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the block was produced by validators/miners. Format: TIMESTAMP_NTZ (no timezone) Precision: Second-level accuracy Reliability: Set by block producer Can have minor variations (±15 seconds) Always increasing (newer blocks = later timestamps) Best Practices: Note: Use for time-series analysis, but be aware that block production rates vary by chain. |
| TX_HASH | TEXT | Unique 66-character identifier for the transaction. Format: 0x + 64 hexadecimal characters Usage: Primary key for transaction lookups Join key for traces, logs, and token transfers Immutable once confirmed Example: 0x5c504ed432cb51138bcf09aa5e8a410dd4a1e204ef84bfed1be16dfba1b22060 |
| TX_POSITION | NUMBER | Zero-indexed position of transaction within its block. Insights: Position 0: First transaction in block MEV bots often target early positions Bundle transactions appear consecutively Useful for analyzing transaction ordering |
| TRACE_INDEX | NUMBER | Sequential index of trace within the transaction’s execution. Example: 3 |
| FROM_ADDRESS | TEXT | Address that initiated this specific internal call. Example: ‘0x7a250d5630b4cf539739df2c5dacb4c659f2488d’ |
| FROM_ADDRESS_NAME | TEXT | The name of the address that initiated the trace, if the contract has a name() function. |
| TO_ADDRESS | TEXT | Destination address for this internal call. Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ |
| TO_ADDRESS_NAME | TEXT | The name of the address that received the trace, if the contract has a name() function. |
| INPUT | TEXT | Hex-encoded input data for this trace (function call data). Example: ‘0xa9059cbb0000000000000000000000001234567890123456789012345678901234567890’ |
| OUTPUT | TEXT | Hex-encoded output data from trace execution. Example: ‘0x0000000000000000000000000000000000000000000000000000000000000001’ |
| FULL_DECODED_TRACE | VARIANT | The full json object of the decoded trace, including both input and output data. |
| FUNCTION_NAME | TEXT | The name of the function called in the trace. |
| DECODED_INPUT_DATA | VARIANT | Decoded input data for the trace. |
| DECODED_OUTPUT_DATA | VARIANT | Decoded output data for the trace. |
| TYPE | TEXT | The type of EVM operation performed. Example: ‘CALL’ |
| SUB_TRACES | NUMBER | Count of immediate child traces spawned by this trace. Example: 2 |
| VALUE | FLOAT | Amount of native tokens transferred, in token units (not Wei). Key Points: 0 for most contract interactions >0 for native token transfers or payable functions Already converted from Wei (divided by 1e18) Use value_precise for exact amounts Example Query: |
| VALUE_PRECISE_RAW | TEXT | String representation of numeric values preserving exact precision without any adjustments. Format: VARCHAR containing numeric string Purpose: Prevents floating-point precision loss due to snowflake limitations Contains: Raw blockchain values (usually in smallest unit) Example Values: “1000000000000000000” = 1 ETH in Wei “50000000” = 50 USDC (6 decimals) Usage: |
| VALUE_PRECISE | TEXT | String representation of numeric values adjusted for human readability while maintaining precision. Format: VARCHAR containing decimal string Adjustments: Converted from smallest unit to standard unit Purpose: Human-readable values without precision loss Example Values: “1.0” = 1 ETH (converted from Wei) “50.0” = 50 USDC (converted from 6 decimal places) Best Practices: |
| GAS | NUMBER | Gas allocated to this specific trace execution. Example: 250000 |
| GAS_USED | NUMBER | Actual gas consumed by this trace execution. Example: 125673 |
| TRACE_SUCCEEDED | BOOLEAN | Boolean indicating if the trace executed successfully. Example: true |
| ERROR_REASON | TEXT | Technical reason for trace failure. Example: ‘Out of gas’ |
| TX_SUCCEEDED | BOOLEAN | Boolean indicator of transaction success. Values: TRUE: Transaction executed successfully FALSE: Transaction failed/reverted |
| EZ_DECODED_TRACES_ID | TEXT | Primary key - unique identifier for each row ensuring data integrity. Format: Usually VARCHAR containing composite key generated using MD5 hash of the relevant columns. Example: MD5(blocknumber, txhash, trace_index) Usage: Deduplication in incremental loads Join operations for data quality checks Troubleshooting specific records Important: Implementation varies by table - check table-specific documentation. |
| INSERTED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp when the record was first added to the Flipside database. Format: TIMESTAMP_NTZ Use Cases: Data freshness monitoring Incremental processing markers Debugging data pipeline issues SLA tracking Query Example: |
| MODIFIED_TIMESTAMP | TIMESTAMP_NTZ | UTC timestamp of the most recent update to this record. Format: TIMESTAMP_NTZ Triggers for Updates: Data corrections Enrichment additions Reprocessing for accuracy Schema migrations Monitoring Usage: |
