| 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. |
| 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 |
| 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: |
| BRIDGE_ADDRESS | TEXT | The smart contract address handling the bridge operation. Example: ‘0x296f55f8fb28e498b858d0bcda06d955b2cb3f97’ |
| EVENT_NAME | TEXT | The event name as defined in the contract’s ABI. Format: PascalCase event identifier Examples: Transfer - Token transfers Swap - DEX trades OwnershipTransferred - Admin changes Approval - Token approvals Usage Pattern: |
| PLATFORM | TEXT | The protocol or application facilitating the cross-chain bridge transfer. Example: ‘stargate’ |
| PROTOCOL | TEXT | PROTOCOL column |
| PROTOCOL_VERSION | TEXT | PROTOCOL_VERSION column |
| SENDER | TEXT | The address that directly sent tokens to the bridge contract. Example: ‘0xabcdefabcdefabcdefabcdefabcdefabcdefabcd’ |
| RECEIVER | TEXT | The address designated to receive tokens on the destination chain (or on the source chain, for intermediate steps). Example: ‘0x9876543210987654321098765432109876543210’ |
| DESTINATION_CHAIN_RECEIVER | TEXT | The final recipient address on the destination blockchain. Example: ‘0xfedcbafedcbafedcbafedcbafedcbafedcbafed’ |
| DESTINATION_CHAIN | TEXT | The target blockchain network for the bridged assets. Example: ‘arbitrum’ |
| DESTINATION_CHAIN_ID | TEXT | The numeric identifier for the destination blockchain. Example: 42161 |
| TOKEN_ADDRESS | TEXT | The contract address of the token being bridged. Example: ‘0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48’ |
| TOKEN_SYMBOL | TEXT | The symbol identifier for the bridged token. Example: ‘USDC’ |
| AMOUNT_UNADJ | FLOAT | The raw token amount without decimal adjustment. Example: 1000000 |
| AMOUNT | FLOAT | The decimal-adjusted amount of tokens bridged. Example: 1.0 |
| AMOUNT_USD | FLOAT | The hourly close USD value of bridged tokens at the time of the transaction. Example: 1000.50 |
| TOKEN_IS_VERIFIED | BOOLEAN | Whether the token is verified by the Flipside team. Example: true |
| EZ_BRIDGE_ACTIVITY_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: |