Internal Transactions | Ethereum & EVM Chains Data

**Dataset Overview**

BlockDB Canonical Raw Internal Transactions delivers full call-trace decomposition of every EVM transaction, captured via debug_traceTransaction and made queryable directly in Snowflake. Each record represents a single internal call frame within a transaction - covering CALL, DELEGATECALL, STATICCALL, CREATE, and CREATE2 - with the exact position in the call tree (TRACE_ADDRESS), value transferred in wei, gas allocated and consumed, input and output data, and error messages for reverted frames. This dataset exposes the full internal execution flow that is invisible at the transaction level, enabling MEV path reconstruction, internal ETH transfer tracking, and contract creation analysis.

<p><br/></p>

**Sample Notice**

This dataset contains **a small sample** of the full BlockDB Raw Internal Transactions dataset. It is provided **for evaluation, research, and interoperability testing only**. If you need full historical coverage, real-time streaming, or end-of-day (EOD) exports please contact us via contact form on Snowflake Marketplace.

<p><br/></p>

**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.

<p><br/></p>

**Join Keys**

(BLOCK_NUMBER, TX_INDEX) → BLOCKDB0102_TRANSACTIONS_V1 for transaction-level context and execution status.

**Lineage**

Each internal transaction record includes a deterministic _TRACING_ID, linking it to the parent transaction and block lineage chain. This ensures verifiable traceability and reproducibility for every downstream record derived from call-trace data.

<p><br/></p>

**Quality**

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