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

Dataset Overview
Each transaction entry reflects the exact canonical form of the transaction as included in a block, including sender/recipient addresses, gas usage, execution status, transaction type, and (when applicable) created contract addresses.

All records include a deterministic _tracing_id that links each row to its genesis source event, enabling full reconstruction of execution flow and downstream derivations.

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:
• tx_hash BYTEA - 32-byte Keccak-256 transaction hash
• from_address BYTEA - 20-byte sender address
• to_address BYTEA - 20-byte recipient address (NULL for contract creation)
• block_number BIGINT - Block number containing the transaction
• tx_index INTEGER - Zero-based index of the transaction within the block
• created_contract_address BYTEA - 20-byte contract address created by this transaction (if applicable)
• gas_used BIGINT - Gas consumed during transaction execution
• effective_gas_price_wei NUMERIC(38,0) - Final gas price paid in wei
• status_success BOOLEAN - TRUE if successful, FALSE if reverted, NULL for pre-Byzantium blocks
• root BYTEA - Post-transaction state root for pre-Byzantium blocks (NULL otherwise)
• tx_type SMALLINT - Transaction type (e.g., 1 = legacy, 2 = EIP-1559)
• _tracing_id BYTEA - Deterministic lineage identifier for this transaction
• _created_at TIMESTAMPTZ - Record creation timestamp
• _updated_at TIMESTAMPTZ - Record last update timestamp

Notes
• All binary values can be converted to hex via encode(column, 'hex') for readability.
• Unique constraint ensures canonical (block_number, tx_index) ordering.
• tx_index and block inclusion can be directly verified with canonical RLP.

Lineage
Each tx 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
• Ground-truth layer for swaps, liquidity, and token analytics
• Backtesting models using canonical transaction flow
• Gas market analysis (EIP-1559, congestion modeling, MEV impact)
• Contract deployment tracking and behavior analysis

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