Dataset ID

DatasetId Enumeration

Defines the canonical dataset identifiers used across Historic API and WebSocket payloads (e.g., the dataset / dataset_id field). Each identifier maps to a documented REST endpoint and Postgres table in blockdb_evm. Prefix indicates the functional domain:

01xx — base chain primitives (blocks, transactions, logs, internal traces, contracts, function results)
02xx — token and pool metadata (ERC-20/721/1155, pools, fee terms)
03xx — reserves, swap prints, swap fees, transfers, flash loans
04xx — token-to-token OHLC, per-pool VWAP time buckets, pool yields (0411)
05xx — cross-pool token-to-token VWAP (aggregated across venues)
06xx — token-to-fiat (USD) VWAP
07xx — pool TVL in USD
08xx — arbitrage path definitions (0801) and path status (0802; same DDL family as 0801)
09xx — arbitrage opportunities

Value	Table	Description	Notes
`0101`	`blockdb_evm.b0101_blocks_v1`	Canonical block headers and integrity metadata.	`POST /evm/raw/blocks`
`0102`	`blockdb_evm.b0102_transactions_v1`	Executed transactions with gas, status, and calldata.	`POST /evm/raw/transactions`
`0103`	`blockdb_evm.b0103_logs_v1`	Event logs emitted by smart contracts.	`POST /evm/raw/logs`
`0111`	`blockdb_evm.b0111_internal_transactions_v1`	Internal transactions (call traces).	`POST /evm/raw/internal-transactions`
`0121`	`blockdb_evm.b0121_contracts_v1`	Contract deployments (CREATE/CREATE2), keyed by `contract_id`.	`POST /evm/raw/contracts`
`0122`	`blockdb_evm.b0122_function_results_v1`	Contract call return values versioned by block.	`POST /evm/raw/function-results`
`0201`	`blockdb_evm.b0201_erc20_tokens_v1`	ERC-20 token metadata.	`POST /evm/entities/tokens/erc20`
`0202`	`blockdb_evm.b0202_erc721_tokens_v1`	ERC-721 collection metadata.	`POST /evm/entities/tokens/erc721`
`0203`	`blockdb_evm.b0203_erc1155_tokens_v1`	ERC-1155 contract metadata.	`POST /evm/entities/tokens/erc1155`
`0211`	`blockdb_evm.b0211_liquidity_pools_v1`	Liquidity pool registry.	`POST /evm/entities/pools`
`0212`	`blockdb_evm.b0212_liquidity_pools_fee_terms_v1`	Versioned pool fee terms.	`POST /evm/entities/pools/fee-terms`
`0301`	`blockdb_evm.b0301_liquidity_pools_reserves_v1`	Pool reserve / state snapshots. Companion details: `b0301_liquidity_pools_reserves_details_v1` (join on `snapshot_id` = `_tracing_id`).	`POST /evm/reserves`
`0302`	`blockdb_evm.b0302_token_to_token_prices_swap_prints_v1`	Executed swap prints (realized prices).	`POST /evm/prices/spot/crypto/prints`
`0303`	`blockdb_evm.b0303_liquidity_pools_swap_fees_v1`	Per-swap fee accounting.	`POST /evm/swaps/fees`
`0304`	`blockdb_evm.b0304_token_transfers_v1`	Token transfers (native, ERC-20/721/1155).	`POST /evm/transfers/token-transfers`
`0305`	`blockdb_evm.b0305_flash_loan_prints_v1`	Flash loan borrow/repay prints.	`POST /evm/flash-loans/prints`
`0404`	`blockdb_evm.b0404_token_to_token_prices_ohlc_v1`	Time-bucketed OHLC per pool and direction.	`POST /evm/prices/spot/crypto/ohlc`
`0405`	`blockdb_evm.b0405_token_to_token_vwap_v1`	Time-bucketed token-to-token VWAP.	`POST /evm/prices/spot/crypto/vwap`
`0411`	`blockdb_evm.b0411_liquidity_pools_yields_v1`	Pool yield / ROI predictions.	`POST /evm/yields`
`0505`	`blockdb_evm.b0505_token_to_token_cross_pool_vwap_v1`	Cross-venue token-to-token VWAP (all pools aggregated).	`POST /evm/prices/spot/crypto/vwap-aggregate`
`0605`	`blockdb_evm.b0605_token_to_fiat_vwap`	Token-to-USD VWAP time buckets.	`POST /evm/prices/spot/fiat/vwap`
`0701`	`blockdb_evm.b0701_liquidity_pools_tvl_usd_v1`	Pool TVL snapshots in USD.	`POST /evm/tvl`
`0801`	`blockdb_evm.b0801_arb_paths_v1`	Arbitrage path definitions (topology).	`POST /evm/arb/paths`
`0802`	`blockdb_evm.b0801_arb_path_status_v1`	Path active/inactive status events. Same DDL family as `0801`.	`POST /evm/arb/path-status`
`0901`	`blockdb_evm.b0901_arb_opportunities_v1`	Arbitrage opportunities per path and position.	`POST /evm/arb/opportunities`

Usage Notes

For a full tabular index (same IDs and tables), see Dataset index.
Responses that expose a dataset field use one of the identifiers above (or the full table name, e.g. blockdb_evm.b0201_erc20_tokens_v1).
New datasets follow the same prefix scheme; clients should tolerate unknown IDs to remain forward compatible.
Use this enumeration to drive UI labels and access control lists rather than hardcoding endpoint prefixes.

Overview

SDKs

Account & Usage

EVM Endpoints

Enumerations

DatasetId Enumeration

Usage Notes

​DatasetId Enumeration

​Usage Notes

DatasetId Enumeration

Usage Notes