Notable Bitcoin Addresses by On-Chain Balance

Bitcoin Whale Watchlist

Track known and notable Bitcoin addresses using public on-chain data. This watchlist shows address-level balances and activity, not confirmed Bitcoin owners.

Watchlist size
25addresses
Loading on-chain data
Last updated: Waiting for price data
Important: this page tracks Bitcoin addresses, not people or confirmed owners. Address labels may come from public third-party sources and can be incomplete or wrong. One person or institution can control many addresses, and exchange or custodian addresses may represent funds for many users.

Known and notable Bitcoin addresses

Current balances are calculated from public address statistics. USD values are estimates based on reference BTC/USD pricing.

Loading Bitcoin whale watchlist data...

Last updatedWaiting for price data
On-chain sourceBlockstream-compatible Esplora API
Price sourceBTC/USD reference pricing

How this watchlist works

1Bitcoin.xyz stores a small curated list of notable Bitcoin addresses, then refreshes address-level balances through a server-side API. The page avoids owner-ranking claims because public address data does not prove final ownership. To translate small BTC balances into sats, use the Satoshi to Bitcoin Converter.

FAQs

Is this a list of the biggest Bitcoin owners?

No. This is a watchlist of notable Bitcoin addresses. A Bitcoin address is not the same as a person, company, exchange, or final owner.

Why can’t Bitcoin whale ownership be confirmed from an address alone?

Bitcoin addresses are public, but ownership is usually inferred from labels, exchange disclosures, public reporting, and chain analysis. One entity can control many addresses, and one custodian address can represent many users.

How are Bitcoin address balances calculated?

The page uses public address statistics. Balance is calculated from funded outputs minus spent outputs, including confirmed chain data and mempool data where available.

How often is the Bitcoin Whale Watchlist updated?

The page fetches current address data through a cached server-side API. Data may be delayed because public APIs and cache windows are used to keep the page lightweight.