| | --- |
| | license: cc-by-nc-4.0 |
| | tags: |
| | - ethereum |
| | - evm |
| | - blockchain |
| | - cryptocurrency |
| | - crypto |
| | - onchain-data |
| | - tabular |
| | - timeseries |
| | - datasets |
| | - pandas |
| | - polars |
| | - duckdb |
| | pretty_name: BlockDB Token Transfers - Sample |
| | size_categories: |
| | - 10M<n<100M |
| | --- |
| | |
| |  |
| |
|
| | ## Sample Notice |
| |
|
| | This dataset contains **a small sample** of the full BlockDB Token Transfers 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 |
| | Unified token transfer table covering all transfer types in a single normalized schema. Each row represents one transfer event sourced from transactions, internal transactions, or transfer logs — covering native ETH, ERC-20, ERC-721, and ERC-1155 transfers. Only transfers for identified contract addresses are included. |
| |
|
| | Every transfer 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: |
| |
|
| | • id BIGINT – Surrogate primary key (auto-generated) |
| | • block_number BIGINT – Block where the transfer occurred |
| | • 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 transaction receipt; null for native or internal tx transfers |
| | • trace_address TEXT – Trace address for internal tx transfers (e.g., "0", "0.1"); null for other types |
| | • from_address BYTEA – Sender address (20 bytes) |
| | • to_address BYTEA – Recipient address (20 bytes) |
| | • token_address BYTEA – Token contract address (20 bytes); null for native ETH transfers |
| | • amount_raw NUMERIC(78,0) – Raw amount in smallest unit (wei for native, raw uint256 for ERC-20/1155) |
| | • amount_adj TEXT – Decimal-adjusted amount; null if decimals unknown or NFT |
| | • token_id NUMERIC(78,0) – Token ID for ERC-721 and ERC-1155; null for native/ERC-20 |
| | • transfer_type TEXT – Transfer type: native_tx, native_internal, erc20, erc721, erc1155 |
| | • _tracing_id BYTEA – Tracing ID of this transfer record |
| | • _parent_tracing_ids BYTEA[] – Tracing IDs of the parent records leading to this transfer record |
| | • _created_at TIMESTAMPTZ – Record creation timestamp |
| | • _updated_at TIMESTAMPTZ – Record last update timestamp |
| | |
| |
|
| | ### Notes |
| | • transfer_type distinguishes native ETH from top-level transactions (native_tx) vs. internal calls (native_internal). |
| | • amount_adj is null for NFTs (ERC-721) and when token decimals cannot be determined. |
| | • FK: (block_number, tx_index) → blockdb_evm.b0102_transactions_v1. |
| | • Binary values can be rendered as hex via encode(column, 'hex') in SQL. |
| | |
| |
|
| | ## Lineage |
| | Each transfer record includes deterministic _tracing_id and _parent_tracing_ids, providing: |
| | |
| | • Provenance tracking from raw transactions, internal calls, and logs to normalized transfer events |
| | • Reproducible analytics and signal extraction |
| | • Cross-system consistency checks (RPC vs. indexers vs. internal warehouses) |
| | |
| | |
| | ## Common Use Cases |
| | • Wallet balance and flow analytics across all token standards |
| | • Token movement and holder tracking |
| | • Compliance and attribution (native + ERC-20/721/1155 in one table) |
| | • MEV and arbitrage flow reconstruction |
| | • Portfolio tracking and tax reporting |
| | |
| | |
| | ## Quality |
| | • Verifiable lineage: deterministic cryptographic hashes per row |
| | • Reorg-aware ingestion: continuity and consistency across forks |
| | • Complete historical coverage: from chain genesis to present |
| | |
