Quicknode

June 23, 2026 — 3 min read

You have a Quicknode endpoint. For most workloads, that is enough.

But address-level data is different. Transaction history by address, balances across many addresses, deposit confirmation, UTXO lookups. None of that is what raw RPC was built to serve.

Wallet and payment teams run into this consistently. Balance queries are not possible through native RPC methods. The workaround works. Repeated calls, block scanning, a custom database, UTXO tracking logic. But it compounds. Engineering cost that grows with your product and never returns.

Blockbook indexes addresses so your app does not have to reconstruct them from raw blocks.

Skip the custom indexer

Blockbook is a blockchain indexer originally built by Trezor for wallet infrastructure. Quicknode runs it as a managed add-on across six chains: Bitcoin, Bitcoin Cash, Dogecoin, Litecoin, Zcash, and Ethereum.

One API call returns full transaction history, current balance, totals received and sent, and unconfirmed activity. Supports addresses and xpub, so you can query an entire wallet from a single descriptor. It attaches to the Quicknode endpoint you already use. No custom indexer, no extra infrastructure, nothing to maintain.

New to Blockbook? Start here.

What changed in June

REST is now live

Blockbook's open-source software is natively REST. That is how Trezor built it. Quicknode's original implementation exposed only a JSON-RPC interface on top of that. Developers migrating from self-hosted Blockbook had to rewrite their existing REST calls to JSON-RPC just to move to Quicknode.

That is no longer the case.

Both interfaces now work on the same endpoint. Call the REST API directly:

curl -X GET \
"https://YOUR_QUICKNODE_ENDPOINT.com/addon/3/api/v2/address/bc1p72h09wplu60qdxyr8q3ftgdhga7jxnjhdz08qs4u9we9q3lzmqmqa4yzj6?details=txids"

Or stay on JSON-RPC:

curl -X POST "https://YOUR_QUICKNODE_ENDPOINT.com" \
  -H "Content-Type: application/json" \
  --data '{"method":"bb_getAddress","params":["bc1p72h09wplu60qdxyr8q3ftgdhga7jxnjhdz08qs4u9we9q3lzmqmqa4yzj6",{"details":"txids"}],"id":1,"jsonrpc":"2.0"}'

Your stack, your interface.

Four new methods

Full method reference in the docs.

Up to 30% faster responses

Blockbook responses on Quicknode are now up to 30% faster. That covers address queries, transaction lookups, and UTXO retrieval. The calls your product makes most. Nothing changes on your end.

Migrating from self-hosted Blockbook

Running your own Blockbook server means you own the index. You also own every sync failure, every upgrade, and every 2AM page.

Quicknode manages the index, handles chain upgrades, and monitors the infrastructure. And now your existing REST calls work directly on your Quicknode endpoint. Zero code changes. Blockbook starts at $75/month. Add the chains you need, remove anytime.

If you are running self-hosted Blockbook today, REST support removes the last reason not to migrate.

Who this is for

The teams who need Blockbook most are the ones where address visibility is the product. Wallets querying transaction history and balances by address or xpub. Exchanges tracking incoming deposits and running confirmation workflows. Block explorers that need full address history on demand. Payment processors and reconciliation platforms monitoring transactions at scale.

Commencer

Already on Quicknode? Add Blockbook to your existing endpoint in one click. Add Blockbook →

New to Quicknode? Sign up free. Blockbook starts at $75/month. Start building for free →

Ready to build? REST and JSON-RPC references, method details, and setup instructions at quicknode.com/docs/bitcoin/blockbook/overview.