BlockDB/ERC721-Tokens-Ethereum-And-EVM-Cryptocurrency-Data

Sample Notice

This dataset contains a small sample of the full BlockDB ERC-721 Tokens 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

Catalog of ERC-721 (NFT) token contracts discovered on-chain. Each row represents a unique ERC-721 token collection with its metadata (name, symbol, base token URI) and provenance information indicating where the token was first recognized or derived from on-chain activity.

Every token record includes deterministic tracing IDs that link the record to its genesis event and upstream sources, enabling full provenance tracking for downstream analytics.

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_address BYTEA – 20-byte address of the ERC-721 token contract (primary key)
•	block_number BIGINT – Block of the log attributed as the genesis/recognition point
•	block_time TIMESTAMPTZ – UTC timestamp when the block was mined
•	tx_index INTEGER – Transaction index within the block
•	log_index INTEGER – Log index within the block
•	name TEXT – Name of the ERC-721 token collection
•	symbol TEXT – Symbol/ticker of the ERC-721 token
•	base_token_uri TEXT – Base URI for token metadata, if any
•	_tracing_id BYTEA – Tracing ID of this ERC-721 token record
•	_genesis_tracing_ids BYTEA[] – Tracing IDs of the genesis records leading to this token record
•	_parent_tracing_ids BYTEA[] – Tracing IDs of the parent records leading to this token record
•	_created_at TIMESTAMPTZ – Record creation timestamp
•	_updated_at TIMESTAMPTZ – Record last update timestamp

Notes

•	Primary key: contract_address guarantees uniqueness per token collection.
•	Indexes on (block_number, tx_index, log_index), block_number, and block_time support fast lookups.
•	Binary values can be rendered as hex via encode(column, 'hex') in SQL for display or downstream joins.

Lineage

Each token record includes deterministic _tracing_id, _genesis_tracing_ids, and _parent_tracing_ids, providing:

•	Provenance tracking from raw logs to decoded token metadata
•	Reproducible analytics and signal extraction
•	Cross-system consistency checks (RPC vs. indexers vs. internal warehouses)

Common Use Cases

•	Building NFT collection registries and metadata catalogs
•	NFT market analytics and collection tracking
•	NFT discovery and new collection detection
•	Wallet portfolio tracking for NFT holdings

Quality

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