BitcoinDatabase.com

On-chain metrics · Rich list

Bitcoin rich list with the largest balances ranked

The Bitcoin rich list ranks addresses by balance, from the largest holders down. BitcoinDatabase builds it from the fully-indexed chain, so every balance is exact to the satoshi and reflects the current chain tip. Where an address clusters to a known exchange, miner or service, we attach a label so you can tell a cold-storage exchange wallet from an individual address.

or try it below ↓

REST API · SQL · dashboards · address history from genesis

Query Console
btc
try:

Hit Run to query the Bitcoin blockchain.

Live from the chain for .

BTC

Balance trail

informational on-chain data · not financial advice

REST API · SQL · dashboards, one indexed dataset. Reading the chain ...

Query the top N over the API, slice it in SQL by balance band or label, or browse it on a dashboard, and pull historical snapshots to see how the distribution shifts over time. This is informational on-chain analytics, not financial advice or any claim about who controls an address.

REST API SQL DASHBOARDS WEBHOOKS CSV EXPORT

History from genesis queryable in seconds

On-chain data not financial advice

Why it works

What you get with Rich list

Exact, current ranking

Balances are computed to the satoshi from the indexed chain and reflect the current tip, so the ranking is precise rather than estimated.

Labels add context

Known exchange, miner and service labels help you separate institutional cold storage from other addresses, as informational context only.

History and distribution

Pull historical snapshots and balance-band breakdowns to study how supply concentration and the wealth distribution change over time.

What it handles

The indexed Bitcoin chain, queryable your way

Look up an address, a transaction, a UTXO, the rich list or an on-chain metric, by REST API, SQL or dashboard. The same authoritative data, reconciled block-by-block against the canonical chain, without running a node.

  • Rank addresses by exact balance
  • Filter by balance band or entity label
  • Tell exchange wallets from other addresses
  • Pull historical rich-list snapshots
  • Query via API, SQL or dashboard
GET /v1/address/{addr} query result
200 · JSON
{
  "address": "bc1qxy2k…l0wdv8",
  "balance_btc": 68432.10,
  "balance_usd": 4612165420,
  "tx_count": 1284,
  "unspent_outputs": 37,
  "first_seen": "2014-02-09"
}
indexed from genesis · to the satoshi ✓ reconciled block-by-block

Why BitcoinDatabase

One platform, queryable three ways

Not a raw node to sync, not an indexer to build, and not five vendors to stitch together. The fully-indexed Bitcoin blockchain, available as a REST API, as SQL, and as dashboards, on one authoritative dataset.

REST API

Typed JSON for addresses, transactions, balances, UTXOs and metrics. Drop it into apps, wallets, explorers and agents with curl, Python or any HTTP client.

SQL access

Run SQL directly against the indexed Bitcoin dataset for ad-hoc analysis, cohorts and exports, the same data the API and dashboards read from.

Compliance-first

Informational on-chain data and analytics only. Entity labels and flow tracing are framed as tooling to support a regulated team's own review, not accusations.

Good questions

Questions about Rich list

Each balance is computed to the satoshi from the fully-indexed chain and reflects the current tip, so the ranking is exact, not estimated. You can also pull historical snapshots to track changes over time.
No. Where possible we add labels such as a known exchange or miner as informational context from clustering. It makes no claim about which individual controls an address, and it is analytics data, not advice.
Almost never. The largest balances are overwhelmingly exchange and custodian cold-storage addresses holding coins for millions of customers, which is why a label matters more than a rank. Reading the top of the list as a ranking of individuals gets it backwards more often than it gets it right.
Far more addresses than holders, and the two are not comparable. One person using an HD wallet accumulates a new address on almost every transaction, while one exchange address can hold coins for millions of people. Address counts measure ledger entries, not owners, in both directions at once.
Mostly because they rank different things. Some rank raw addresses, others rank clustered entities that group addresses believed to share an owner, and clustering is inference rather than fact. Balance-band cutoffs and how each site handles exchange labels then move the numbers again.
Yes, within the indexed chain, which grows with every new block. Balances there can be reconstructed at a past height, so you can pull a rich-list snapshot for a date in that range and compare distributions across time. That is how supply-concentration studies are built without trusting a single vendor snapshot.
GET /v1/addresses/top returns 25 addresses by default and up to 200 with the limit parameter, at 1 credit a call. The response states its own scope: it ranks the outputs indexed so far, not the entire UTXO set, and says so in a note field. Full balances for any single address come from the address endpoint, with history back to 2009.
Mostly, yes. On 28 September 2026 at block 969,059 five exchange cold addresses we track held 685,431.54334626 BTC between them. The largest, 34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo, held 248,597.59262947 BTC across 5,586 transactions. Those balances belong to many customers, which is why a rich list is a map of custody, not of individual wealth.
Usually dust: a stranger sends a few hundred satoshis to a famous address so the output shows up in wallet histories. On 28 September 2026 a 546 satoshi payment to one top address, paying 0.162 sat/vB, had been unconfirmed for more than 900 blocks. Filter outputs this small before you count activity on a large address, or quiet cold wallets look busy.

Explore more

More ways to query Bitcoin with BitcoinDatabase

Stop running a node. Just query Bitcoin.

Run your first query now and get on-chain data back by REST API, SQL or dashboard, with address history back to the genesis block over REST. Informational on-chain data only, not financial advice.

See pricing

History from genesis over REST · SQL · dashboards · addresses, transactions, UTXOs, metrics