| 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 |
| 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: |
| EVENT_TYPE | TEXT | The specific type of NFT transaction that occurred. Common values include ‘sale’, ‘bid_won’, ‘redeem’, and ‘mint’. Example: ‘sale’ |
| PLATFORM_ADDRESS | TEXT | The smart contract address of the marketplace facilitating the sale. Platforms may have multiple contracts for different versions. Example: ‘0x00000000006c3852cbef3e08e8df289169ede581’ |
| PLATFORM_NAME | TEXT | The marketplace or platform where the NFT sale occurred. Standardized to lowercase with no spaces. Example: ‘opensea’ |
| PLATFORM_EXCHANGE_VERSION | TEXT | The version identifier of the marketplace contract. Tracks protocol versions and upgrades. Example: ‘seaport15’ |
| AGGREGATOR_NAME | TEXT | The NFT aggregator platform that routed the transaction. NULL indicates direct platform interaction. Example: ‘gem’ |
| SELLER_ADDRESS | TEXT | The blockchain address that sold the NFT. Example: ‘0x1234567890123456789012345678901234567890’ |
| BUYER_ADDRESS | TEXT | The blockchain address that purchased the NFT. Example: ‘0x1234567890123456789012345678901234567890’ |
| CONTRACT_ADDRESS | TEXT | The smart contract address of the NFT collection. Supports ERC-721, ERC-1155, and custom implementations. Example: ‘0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d’ |
| NAME | TEXT | The name of the NFT collection or project. May be NULL for unverified collections. Example: ‘Bored Ape Yacht Club’ |
| TOKEN_ID | TEXT | The unique identifier of the specific NFT within its collection. Format is numeric string. Example: ‘1234’ |
| QUANTITY | TEXT | The number of tokens sold in the transaction. Primarily relevant for ERC-1155 tokens. Example: ‘1’ |
| TOKEN_STANDARD | TEXT | The technical standard implemented by the NFT contract. Common values include ‘erc721’, ‘erc1155’, ‘cryptopunks’, and ‘legacy’. Example: ‘erc721’ |
| CURRENCY_SYMBOL | TEXT | The symbol of the token used for payment. Example: ‘ETH’ |
| CURRENCY_ADDRESS | TEXT | The contract address of the payment token. Shows ‘ETH’ for native ETH payments. Example: ‘0xa0b86a33e6776a1e7f9f0b8b8b8b8b8b8b8b8b8b’ |
| PRICE | FLOAT | The sale price in the payment currency, including platform and creator fees. Raw price before USD conversion. Example: 2.5 |
| PRICE_USD | FLOAT | The sale price converted to USD at transaction time, including platform and creator fees. May be NULL for missing price data. Example: 4250.75 |
| TOTAL_FEES | FLOAT | The combined platform and creator fees in the payment currency. Example: 0.125 |
| PLATFORM_FEE | FLOAT | The fee charged by the marketplace in the payment currency. Typically 2-2.5% of sale price. Example: 0.05 |
| CREATOR_FEE | FLOAT | The royalty fee paid to the collection creator in the payment currency. Typically 0-10% of sale price. Example: 0.075 |
| TOTAL_FEES_USD | FLOAT | The combined platform and creator fees converted to USD. Example: 212.54 |
| PLATFORM_FEE_USD | FLOAT | The marketplace fee converted to USD. Example: 85.02 |
| CREATOR_FEE_USD | FLOAT | The royalty fee converted to USD. Example: 127.52 |
| TX_FEE | FLOAT | Total fee paid for transaction execution in native token units. Example: 0.002 |
| TX_FEE_USD | FLOAT | The transaction fee denominated in USD. Use only one instance per transaction to avoid overcounting. Example: 45.32 |
| 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. |
| 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 |
| EZ_NFT_SALES_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: |