BlockDB Coins Tokens Details | Ethereum & EVM Chains | Historical, EOD, Real-Time | Crypto Token ...

Dataset Overview
Canonical on-chain token reference for fungible and non-fungible assets, providing unified structure and lineage for every recognized contract.
Each row represents a unique token or collection, traceable to its genesis event and ABI-decoded metadata.

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.
Includes both native coins (ETH, BNB, AVAX, etc.) and token contracts (ERC-20, ERC-721, ERC-1155, ERC-4626, custom standards).

Schema
List the columns exactly as delivered.
• contract_address BYTEA - PK; 20-byte contract address
• block_number BIGINT - first block where the token was recognized
• block_time TIMESTAMPTZ - UTC timestamp when the block was mined
• tx_index INTEGER - tx index for that event
• log_index INTEGER - log index for that event
• name TEXT - asset name (from ABI or native coin registry)
• symbol TEXT - token symbol or ticker
• decimals SMALLINT - number of decimal places for fungible tokens (NULL for NFTs)
• metadata_uri TEXT - optional field for NFT metadata base URI (if applicable)
• _tracing_id BYTEA - deterministic row-level hash
• _parent_tracing_ids BYTEA[] - hash(es) of immediate parent rows in the derivation graph
• _genesis_tracing_ids BYTEA[] - hash(es) of original sources (genesis of the derivation path)
• _created_at TIMESTAMPTZ - Record creation timestamp.
• _updated_at TIMESTAMPTZ - Record last update timestamp

Notes
• Use encode(contract_address,'hex') for hex presentation.
• Metadata for each token type is retrieved deterministically via ABI decoding or registry sources.
• If the ABI read was unsuccessful, the token is not present in this table.

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
• _genesis_tracing_ids - original on-chain sources
This supports audits and exact reprocessing to source transactions/logs/function calls.

Common Use Cases
• Canonical token registry for normalization across DeFi datasets
• Symbol, name, decimals lookups for accurate unit scaling in analytics
• Cross-chain asset identity resolution
• Foundation for NFT, LP token, and vault datasets
• Integration layer for pricing engines, wallets, and indexers

Quality
• Each row includes a cryptographic hash linking back to raw on-chain events for auditability.
• Tick-level resolution for precision.
• Reorg-aware ingestion ensuring data integrity.
• Complete backfills to chain genesis for consistency.