Skip to main content

​
Overview

BlockDB ships a Postgres schema for every dataset that also powers the Historic REST API. The scripts in /BlockDb.Postgres.Tables.Public are the canonical definitions; each dataset here mirrors the SQL CREATE TABLE statements, constraints, and indexes from that source. All tables follow a <schema>.<dataset_id>_<name>_v<major> naming convention to support multiple chain families at scale:
  • EVM datasets live in blockdb_evm (for example, blockdb_evm.0101_blocks_v1)
  • SVM datasets live in blockdb_svm (for example, blockdb_svm.0101_blocks_v1)
Dataset IDs match the REST API identifiers (0101 for blocks, 0201 for ERC-20 tokens, etc.) so you can map SQL exports to API payloads or lineage metadata.

​
How to use this catalog

  1. Choose your chain family (EVM or SVM).
  2. Open the chain overview to browse datasets and review per-table documentation.
  3. Use dataset IDs to map between SQL tables, API payloads, and lineage records.

EVM dataset index

Browse all EVM tables, grouped by domain (ledger, tokens, reserves, pricing, analytics).

SVM overview

Learn about the Solana (SVM) catalog roadmap and upcoming dataset structure.