Blockchain Data API datasets: choose data for your application
Choose Blockchain Data API datasets for token balances, transfer history, tokenized stocks and other indexed data. Check chain coverage, then open the request reference.
Choose Blockchain Data API datasets by task and check the chain matrix below. For wallet assets, start with token balances and token transfer history; for tokenized stock activity, see the stocks guide. Once you have chosen a dataset, use the Data API reference for request parameters and response schemas, or the Quickstart for your first call.
What's available
- Blocks & transactions — block and transaction data, including event logs and execution traces (where supported).
- Token transfers & balances — ERC-20 transfer history and address balances.
- Token holders — holders and balances per token.
- Tokenized stocks — US stocks and ETFs issued on supported chains as tokens.
- DEX trades & daily prices — decentralized exchange trades and daily prices.
- NFT holdings — current holders and balances.
- Data freshness — how far each dataset lags behind the indexed chain head.
Chain × dataset matrix
Availability of datasets across supported chains:
| Chain | Token transfers | Token balances | Token holders | Tokenized stocks | DEX trades & daily prices | NFT holdings | Traces |
|---|---|---|---|---|---|---|---|
| Arbitrum One RPC and Data API (arb_mainnet) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Base RPC and Data API (base_mainnet) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| BNB Smart Chain RPC and Data API (bsc_mainnet) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Ethereum RPC and Data API (eth_mainnet) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Ethereum Sepolia RPC and Data API (eth_sepolia) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Gnosis RPC and Data API (gnosis_mainnet) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| HyperEVM RPC and Data API (hyperevm_mainnet) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| OP Mainnet RPC and Data API (op_mainnet) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Polygon RPC and Data API (polygon_mainnet) | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
| Robinhood Chain RPC and Data API (robinhood_mainnet) | ✓ | ✗ | ✗ | ✓ | Partial | ✗ | ✓ |
Partial = only some of this dataset's endpoints are enabled on that chain.
Coverage notes
- Ethereum window: coverage for transfers and address transactions is determined by
coverage.from_blockinGET /v1/data/chains; a response that crosses the window start is markedmeta.coverage: "partial". - Traces: available on select chains only, from a certain block onward, with a small number of gaps (see Supported Chains).
✗ means requests return 422 no_coverage (not billed).
See Supported Chains for endpoint URLs, chain IDs, and additional per-chain details.
Next steps
- Quickstart — make your first JSON-RPC and Data API calls.
- Data API reference — endpoints, parameters, and response shapes.
- Supported Chains — service capabilities and network identifiers.
Last updated:
Error Reference
BlockVectra error codes, billing and retry guidance for JSON-RPC, Data API, Push Webhooks, console and faucet, including eth_getLogs block ranges and Webhook replay errors.
Guides
Practical guides and workflows for integrating BlockVectra APIs, managing CU consumption, and building multichain applications.