Indexed Data is Quicknode's collection of structured, queryable onchain datasets. Quicknode processes blockchain activity into records you can use without building and maintaining your own indexer. Asset Transfers is the first dataset documented here.
Datasets and access methods
A dataset defines the information you work with. An access method defines how you retrieve it. For Asset Transfers, these methods do different amounts of work for you: SQL Explorer lets you build a custom query from EVM tables, the SQL API runs that query programmatically, Explorer API provides a curated account-history method, and Streams lets you write a filter that extracts transfers from blockchain data as it is delivered.
The available methods can differ by dataset and network. The coverage table on each dataset page shows what is currently listed as supported.
Available dataset
| Dataset | What it provides | Supported mainnets |
|---|---|---|
| Asset Transfers | Account transfer history, including native, token, NFT, and internal transfers | Ethereum, BNB Smart Chain, Arc, Robinhood Chain, Elysium, Base, and Arbitrum One |
See Asset Transfers for the transfer types, access paths, and a request you can run.
How the data is built
For Asset Transfers, Quicknode connects directly to supported networks and indexes raw blocks, receipts, and traces into structured records. SQL Explorer and Explorer API use the same underlying indexed data for Asset Transfers, but expose it differently: SQL gives you control over the query, while qn_getAssetTransfers returns an optimized, curated JSON-RPC response. Explorer API results include the transaction and block associated with each movement, so you can connect a returned transfer to its onchain source. EVM indexed data extends back to each supported network's genesis block.
The transfer records include native asset movements, ERC-20 transfers, ERC-721 and ERC-1155 NFT transfers, and internal transfers of native value made by contract calls. The exact fields you receive depend on the access method. See the Asset Transfers dataset page and the linked method references for the response format and pagination behavior.
Ways to access Indexed Data
Indexed Data can be queried through different interfaces. Availability depends on the dataset and network.
SQL Explorer users build the transfer query they need from EVM tables. Streams users choose a supported blockchain dataset and write a filter to extract transfers. Check Streams supported chains before configuring a Stream for a particular network.
Other indexed data products
Quicknode also offers indexed APIs with their own setup and references. These are related capabilities; the diagram above shows access methods for Asset Transfers.