| 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 |
| EVENT_INDEX | NUMBER | Zero-based sequential position of the event within a transaction’s execution. Key Facts: Starts at 0 for first event Increments across all contracts in transaction Preserves execution order Essential for deterministic event ordering Usage Example: |
| INTRA_EVENT_INDEX | NUMBER | Position within a batch transfer event, primarily for ERC-1155. Always starts with 1 for single transfers. Example: 1 |
| TOKEN_TRANSFER_TYPE | TEXT | The specific event type emitted by the contract. Values include ‘erc721Transfer’, ‘erc1155TransferSingle’, ‘erc1155TransferBatch’, etc. Example: ‘erc721Transfer’ |
| IS_MINT | BOOLEAN | Boolean flag indicating if this transfer is a minting event (from address is 0x0). Example: true |
| FROM_ADDRESS | TEXT | The address sending/transferring the NFT. Special value of ‘0x0000000000000000000000000000000000000000’ indicates minting event. Example: ‘0x1234567890123456789012345678901234567890’ |
| TO_ADDRESS | TEXT | The address receiving the NFT. Special value of ‘0x0000000000000000000000000000000000000000’ indicates burning event. Example: ‘0x1234567890123456789012345678901234567890’ |
| CONTRACT_ADDRESS | TEXT | The address of the contract that emitted the NFT transfer event. Example: ‘0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d’ |
| TOKEN_ID | TEXT | The unique identifier for a specific NFT within a collection. String format to handle various token_id formats. Example: ‘1234’ |
| QUANTITY | TEXT | The number of NFTs transferred for this specific token_id. Always 1 for ERC-721, can be more for ERC-1155. Example: 1 |
| TOKEN_STANDARD | TEXT | The standard of the NFT. Values include ‘erc721’, ‘erc1155’, ‘cryptopunks’, and ‘legacy’. Example: ‘erc721’ |
| NAME | TEXT | The name of the NFT collection. For Ethereum only, join with nft.dimnftcollection_metadata for token-level details. Example: ‘Bored Ape Yacht Club’ |
| ORIGIN_FUNCTION_SIGNATURE | TEXT | Function signature (first 4 bytes) of the called method. Format: 0x + 8 hex characters Common Signatures: 0xa9059cbb: transfer(address,uint256) 0x095ea7b3: approve(address,uint256) 0x23b872dd: transferFrom(address,address,uint256) Note: NULL for simple transfers or invalid calls |
| ORIGIN_FROM_ADDRESS | TEXT | The externally-owned account (EOA) or contract address that initiated the transaction. Key Points: Always 42 characters (0x + 40 hex chars) Lowercase normalized in all tables Cannot be NULL for valid transactions For contract creation: sender of creation transaction Common Patterns: EOA → EOA: Simple transfer EOA → Contract: User interaction Contract → Contract: Internal calls (see fact_traces) Known addresses: Exchange hot wallets, protocol deployers Query Examples: |
| ORIGIN_TO_ADDRESS | TEXT | The destination address for the transaction - either an EOA or contract address. Special Cases: NULL: Contract creation transaction Contract address: Interacting with smart contract EOA address: Simple transfer or receiving funds Important Patterns: Note: For token transfers, this is the token contract, not the recipient. See eztokentransfers tables for recipient. |
| EZ_NFT_TRANSFERS_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: |