BlockDB Canonical Raw Blocks (Lineage-Verified) | Ethereum & EVM Chains | Historical, EOD, ...

Dataset Overview
Each block entry contains the complete structural and integrity metadata required to reconstruct or verify the block state:
hashes, parent linkage, miner address, gas and size metrics, timestamps, extra data, and lineage identifiers (_tracing_id, _computed_receipt_root).

Chains and Coverage
ETH, BSC, Base, Arbitrum, Unichain, Avalanche, Polygon, Celo, Linea, Optimism (others on request).
Full history from chain genesis; reorg-aware real-time ingestion and updates.

Schema
List of columns exactly as delivered:
• block_number BIGINT - Sequential block number
• block_hash BYTEA - 32-byte block hash
• parent_hash BYTEA - 32-byte parent block hash
• receipts_root BYTEA - Root hash of all receipts in the block
• miner BYTEA - 20-byte miner (beneficiary) address
• gas_limit NUMERIC(78,0) - Maximum gas allowed for the block
• extra_data BYTEA - Arbitrary ≤32-byte payload embedded by the block producer
• size BIGINT - Total block size in bytes (header + transactions + receipts)
• timestamp_utc TIMESTAMPTZ - UTC timestamp when the block was mined
• _tracing_id BYTEA - Deterministic tracing ID of this block record
• _computed_receipt_root BYTEA - Recomputed receipts root (BlockDB integrity check)
• _computed_receipt_timestamp_utc TIMESTAMPTZ - Timestamp when the receipts root was computed or revalidated
• _created_at TIMESTAMPTZ - Record creation timestamp
• _updated_at TIMESTAMPTZ - Record last update timestamp

Notes
• Use encode(block_hash, 'hex') to convert binary values to hex for presentation or joins.
• Every block record is verified against the node RPC.

Lineage
Each block record includes a deterministic _tracing_id, forming the root lineage reference for all derived BlockDB datasets (swaps, liquidity, and token prices).
This ensures verifiable traceability, reproducibility, and proof-of-derivation for every downstream record.

Common Use Cases
• Benchmarking node or indexer consistency across chains
• Establishing canonical ground truth for analytics or compliance systems
• Foundation layer for derived token, swap, and liquidity datasets
• Validating receipts and state integrity with recomputed roots

Quality
• Verifiable lineage: deterministic cryptographic hashes per row
• Reorg-aware ingestion: continuity and consistency across forks
• Complete historical coverage: from chain genesis to present