On-chain metrics · Bitcoin active address data
Bitcoin active addresses: daily active address data and charts
Bitcoin active addresses counts the unique addresses that sent or received coins in a window. It is the most quoted measure of network usage, and the easiest to misread, because an address is not a person.
REST API · SQL · dashboards · indexed from genesis
Hit Run to query the fully-indexed Bitcoin blockchain.
BTC
30-day trend
informational on-chain data · not financial advice
We took one block apart to show how much that matters. Block 963,218 was mined on 19 August 2026 at 20:15:57 UTC with 4,329 transactions in it, and we fetched every one of them. Counted the usual way, as unique addresses appearing as an input or an output, that block contains 12,388 active addresses. Of those, 11,760 appear exactly once. Only 628 show up in more than one transaction. So roughly 95 percent of the addresses that made the block look busy were used a single time and then abandoned, which is precisely what a modern wallet is designed to do: derive a fresh address for every receive, and a fresh change address for every spend.
The consolidation problem is easier to see in one transaction. The largest transaction in that block, by addresses touched, pulled 293 inputs from 285 distinct addresses into a single output worth 0.15191017 BTC, paying a 40,049 satoshi fee to do it. That is one wallet sweeping its own dust into one place. It is one actor taking one action, and it registered 285 active addresses, 2.3 percent of the entire block, without a single payment being made to anybody. Batched exchange withdrawals produce the same distortion pointing the other way, with one entity paying hundreds of customers in one transaction.
Apply the standard entity heuristic, where addresses that co-spend inside one transaction are treated as one owner, and those 12,388 addresses collapse to 9,789 actors. That is a 21 percent overcount, and it is a floor rather than an estimate, because clustering inside a single block can only merge addresses that happened to co-spend within that block. Run the same logic across the full chain and far more of them merge. Nothing here is a flaw in Bitcoin or in the metric. It is what the metric has always measured, which is ledger entries rather than users.
BitcoinDatabase computes active addresses on the fully-indexed chain and gives you all of the definitions rather than one: raw unique addresses, senders and receivers separately, counts with change outputs removed, and entity-adjusted counts built on address clustering. Pull a daily series over REST, rebuild the history since the 2009 genesis block in SQL, or drill from any single day straight down to the addresses that produced the number. This is informational on-chain data and analytics, not financial, investment or trading advice.
Indexed from genesis queryable in seconds
On-chain data not financial advice
Why it works
What you get with Bitcoin active address data
Every definition, not just one
Read raw unique addresses, senders and receivers separately, counts with change outputs stripped out, and entity-adjusted counts that merge addresses believed to share an owner. When a series moves you can see which definition moved it, instead of guessing at a vendor methodology you cannot inspect.
Entity-adjusted, not just unique
Address clustering groups addresses that co-spend into a single actor, which is the closest the public chain gets to counting users rather than ledger entries. Clustering is inference and we say so plainly, but an inferred actor count answers the question people actually mean when they ask how many people used Bitcoin today.
Drill to the addresses behind it
Every daily figure ties back to the exact transactions and addresses that produced it, so you can audit a spike instead of trusting it. When one consolidation sweep or one exchange batch moves the number, you can open the transaction and see it.
Side by side
Four ways to count the same block, four different answers
Every transaction in block 963,218 was fetched and counted first-hand on 19 August 2026. The block was mined at 20:15:57 UTC and holds 4,329 transactions. Each row applies a defensible definition of an active address to that identical set of transactions.
| How you count | Definition applied | Result for block 963,218 | Share of the naive count |
|---|---|---|---|
| Naive unique addresses | Every address appearing as an input or an output, counted once each | 12,388 | 100% |
| Excluding same-transaction change | Drops addresses that received change in a transaction they also funded | 11,533 | 93.10% |
| Entity-adjusted clustering | Addresses that co-spend inside one transaction are merged into one actor | 9,789 | 79.02% |
| Receiving addresses only | Addresses that received coins, ignoring every sender | 8,087 | 65.28% |
| Sending addresses only | Addresses that spent coins, ignoring every recipient | 5,512 | 44.49% |
The entity-adjusted figure is a floor, not a final answer. Clustering here only merges addresses that co-spend inside this one block, so the true overcount across a full day is larger than the 21 percent a single block can prove. All five rows are correct arithmetic on the same 4,329 transactions, which is the point: the definition decides the number before the data does.
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.
- Pull daily, weekly and monthly active address series
- Read entity-adjusted counts next to raw unique addresses
- Rebuild the full history since the 2009 genesis block
- Separate sending addresses from receiving addresses
- Exclude change outputs from the count
- Drill from any day to the exact addresses behind it
- Join active addresses to price, fees and exchange flows in SQL
{
"address": "bc1qxy2k…l0wdv8",
"balance_btc": 68432.10,
"balance_usd": 4612165420,
"tx_count": 1284,
"unspent_outputs": 37,
"first_seen": "2014-02-09"
}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 Bitcoin active address data
Explore more
More ways to query Bitcoin with BitcoinDatabase
Bitcoin transaction volume
Raw, change-adjusted and entity-adjusted on-chain volume series from the indexed chain.
Learn moreOn-chain metrics
Active addresses, realized cap, SOPR, HODL waves and exchange flows.
Learn moreBitcoin address labels
Attach exchange, miner and service labels to addresses, so raw hashes read as entities.
Learn moreBitcoin historical data API
Full-depth history: every block, transaction and metric back to 2009.
Learn moreBitcoin address balance history API
What an address held on any past date, not just what it holds now.
Learn moreDormant Bitcoin wallet and address API
Find addresses whose coins have not moved in years, by last spend rather than last touch.
Learn moreStop running a node. Just query Bitcoin.
Run your first query now and get on-chain data back by REST API, SQL or dashboard, indexed from the genesis block. Informational on-chain data only, not financial advice.
Indexed from genesis · REST · SQL · dashboards · addresses, transactions, UTXOs, metrics