BlockDB/Raw-Function-Results-Ethereum-And-EVM-Cryptocurrency-Data

Sample Notice

This dataset contains a small sample of the full BlockDB Raw Function Results 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

On-chain contract function call return values versioned by block. Each row records the raw output of a deterministic view function call at a specific block height, enabling time-travel queries over any contract's on-chain state. Uses a 26-byte contract_id (consistent with the contracts dataset) to correctly handle metamorphic contracts.

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:

•	contract_id BYTEA – Part of PK; 20 bytes (address) + 4 bytes (creation block BE) + 2 bytes (tx_index BE); links to b0121_contracts_v1
•	block_number BIGINT – Part of PK; block at which the value was read
•	block_time TIMESTAMPTZ – UTC timestamp when the block was mined
•	call_data BYTEA – Part of PK; raw call data used to invoke the function
•	signature_hash BYTEA – 4-byte selector (keccak256(signature)[0..3])
•	result BYTEA – Raw return data from the function call (null if reverted)
•	timestamp_utc TIMESTAMPTZ – UTC timestamp when the function call result was recorded
•	_tracing_id BYTEA – Deterministic tracing ID of this function result record
•	_created_at TIMESTAMPTZ – Record creation timestamp
•	_updated_at TIMESTAMPTZ – Record last update timestamp

Notes

•	Primary key: (contract_id, block_number, call_data) enables point-in-time lookups per contract per call.
•	result is raw ABI-encoded bytes; decode using the ABI for the matching signature_hash.
•	NULL result indicates a reverted call at that block.
•	Use encode(contract_id, 'hex') to convert binary values to hex.

Lineage

Each function result record includes a deterministic _tracing_id, providing:

•	Provenance tracking from raw RPC calls to versioned contract state snapshots
•	Reproducible analytics and signal extraction
•	Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)

Common Use Cases

•	Historical state reconstruction and time-travel queries
•	Token metadata and balance lookups at specific blocks
•	Contract configuration and parameter tracking over time
•	Price oracle and external data feed analysis
•	Governance proposal and voting state tracking

Quality

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