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

Dataset Overview
Full call-trace decomposition of every EVM transaction via debug_traceTransaction. One row per internal call, with the complete call tree position, call type, value transferred, gas used, and input/output data — providing complete internal execution visibility beyond top-level transactions.

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 the columns exactly as delivered.
• block_number BIGINT - PK (part); block number of the parent transaction
• block_time TIMESTAMPTZ - UTC timestamp of the block
• tx_index INTEGER - PK (part); zero-based index of the parent transaction within the block
• trace_address TEXT - PK (part); position in the call tree (e.g., "0", "0.0", "0.1")
• call_type TEXT - type of call: CALL, DELEGATECALL, STATICCALL, CREATE, CREATE2
• from_address BYTEA - address of the caller (20 bytes)
• to_address BYTEA - address of the callee (20 bytes); null for failed CREATE/CREATE2
• value_wei NUMERIC - native value (in wei) transferred in this call
• gas NUMERIC - gas allocated for this call
• gas_used NUMERIC - gas actually consumed by this call
• input BYTEA - input data (calldata) for this call
• output BYTEA - return data from the call (null if reverted)
• error TEXT - error message if the call reverted
• tx_success BOOLEAN - success of the underlying transaction that caused this internal transaction
• _tracing_id BYTEA - deterministic row-level hash
• _created_at TIMESTAMPTZ - Record creation timestamp
• _updated_at TIMESTAMPTZ - Record last update timestamp

Notes
• Use encode(from_address,'hex') or encode(to_address,'hex') for hex presentation.
• trace_address encodes the depth and position: "0" is the first top-level call, "0.1" is the second sub-call of the first call.
• FK: (block_number, tx_index) → blockdb_evm.b0102_transactions_v1

Lineage
Every row has a verifiable path back to the originating raw events via the lineage triple and tracing graph:
• _tracing_id - this row's identity
• _parent_tracing_ids - immediate sources
This supports audits and exact reprocessing to source transactions/logs/function calls.

Common Use Cases
• Contract creation and factory flow analysis
• Internal call graphs and cross-contract dependencies
• Value flow and gas consumption per call
• Debugging failed transactions and revert reasons
• MEV and arbitrage path reconstruction
• Native ETH transfer tracking beyond top-level transactions

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