BlockDB/Raw-Internal-Transactions-Ethereum-And-EVM-Cryptocurrency-Data

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 directly:

📧 support@blockdb.io
🌐 https://www.blockdb.io

Dataset Overview

Full call-trace decomposition of every EVM transaction via debug_traceTransaction. Each row represents a single internal call within a transaction, including the full call tree position, call type, addresses, value transferred, gas allocation and consumption, 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 of columns exactly as delivered:

•	block_number BIGINT – Block number of the parent transaction
•	block_time TIMESTAMPTZ – UTC timestamp when the block was mined
•	tx_index INTEGER – Zero-based index of the parent transaction within the block
•	trace_address TEXT – 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
•	_tracing_id BYTEA – Deterministic tracing ID of this internal transaction record
•	_created_at TIMESTAMPTZ – Record creation timestamp
•	_updated_at TIMESTAMPTZ – Record last update timestamp

Notes

•	Primary key: (block_number, tx_index, trace_address).
•	trace_address encodes call depth and position: "0" is the root call, "0.1" is the second sub-call of the first call.
•	FK: (block_number, tx_index) → blockdb_evm.b0102_transactions_v1.
•	Use encode(from_address, 'hex') or encode(to_address, 'hex') to convert binary values to hex.

Lineage

Each internal transaction record includes a deterministic _tracing_id, providing:

•	Provenance tracking from raw call traces to internal execution events
•	Reproducible analytics and signal extraction
•	Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)

Common Use Cases

•	Contract creation and factory flow analysis
•	Internal call graphs and cross-contract dependencies
•	Value flow and gas consumption per call frame
•	Debugging failed transactions and tracing revert reasons
•	MEV and arbitrage path reconstruction

Quality

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