| 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_HASH | TEXT | The unique 32-byte Keccak-256 hash of the block header, prefixed with ‘0x’. Example: ‘0x4e3a3754410177e6937ef1f84bba68ea139e8d1a2258c5f85db9f1cd715a1bdd’ |
| 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. |
| NETWORK | TEXT | Network identifier within the blockchain (e.g., ‘mainnet’, ‘testnet’). Example: ‘mainnet’ |
| TX_COUNT | NUMBER | Number of transactions included in the block. Example: 142 |
| SIZE | NUMBER | Block size in bytes. Example: 125432 |
| MINER | TEXT | Address that received block rewards. Example: ‘0xea674fdde714fd979de3edf0f56aa9716b898ec8’ |
| MIX_HASH | TEXT | 256-bit hash used in PoW mining process. Post-merge, contains prevRandao for randomness. Example: ‘0x0000000000000000000000000000000000000000000000000000000000000000’ |
| EXTRA_DATA | TEXT | Arbitrary data included by block producer (max 32 bytes). Example: ‘Geth/v1.10.23-stable/linux-amd64/go1.18.5’ |
| PARENT_HASH | TEXT | Hash of the previous block (block_number - 1). Example: ‘0x3d7a3754410177e6937ef1f84bba68ea139e8d1a2258c5f85db9f1cd715a1bee’ |
| GAS_USED | NUMBER | Total gas consumed by all transactions in the block. Example: 15234567 |
| GAS_LIMIT | NUMBER | Maximum gas allowed for all transactions in this block. Example: 30000000 |
| BASE_FEE_PER_GAS | NUMBER | Base fee per gas unit in wei (EIP-1559 chains only). Example: 25000000000 |
| DIFFICULTY | NUMBER | Mining difficulty at block production time. Example: 0 |
| SHA3_UNCLES | TEXT | Keccak-256 hash of uncle blocks list. Example: ‘0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347’ |
| UNCLE_BLOCKS | VARIANT | Array of uncle block headers (PoW only). Example: [] |
| NONCE | NUMBER | Proof-of-Work nonce value. For PoW chains, this demonstrates computational work. Post-merge Ethereum and PoS chains typically show 0x0000000000000000. Example: ‘0x0000000000000000’ |
| RECEIPTS_ROOT | TEXT | Merkle root of all transaction receipts in the block. Example: ‘0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421’ |
| STATE_ROOT | TEXT | Merkle root of the entire blockchain state after executing this block. Example: ‘0xd7f897bbebe1f8d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d4934’ |
| TRANSACTIONS_ROOT | TEXT | Merkle root of all transactions in the block. Example: ‘0x56e81f171bcc55a6ff8345e692c0f86e5b48e01b996cadc001622fb5e363b421’ |
| LOGS_BLOOM | TEXT | 2048-bit bloom filter containing all log addresses and topics from the block’s transactions. Example: ‘0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000’ |
| FACT_BLOCKS_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: |