Bitcoin Active Addresses: What the Metric Actually Counts

Active addresses is the number people reach for when they want to say whether Bitcoin is being used. It appears in research notes, exchange blogs and headlines about network health, usually with no definition attached, as though counting addresses were as simple as counting cars on a road.

It is not, and the gap is not small. So rather than argue about it, we took a single recent block apart transaction by transaction and counted it five different defensible ways. Every figure below comes from that one block, and every one of them is reproducible against any public block explorer.

What are Bitcoin active addresses?

Active addresses is the count of unique addresses that participated in at least one transaction during a chosen window, either as a sender or as a recipient. Coin Metrics, whose definition is among the most widely followed, describes it as the count of unique addresses that were active "either as a recipient or originator of a ledger change" in the interval, and counts an address once no matter how many times it appears.

Read that carefully and the limitation is already visible. It is a count of ledger entries that showed signs of life. Nothing in it refers to a person, a wallet or a user, because the Bitcoin blockchain does not record any of those things. It records addresses.

How is the Bitcoin active addresses metric calculated?

Take every transaction in the window. Collect the addresses on the input side and the output side. Remove duplicates. Report the size of the resulting set.

Each of those steps hides a choice, and the choices are where providers diverge. Does an address that both sends and receives count once or twice? Do change outputs count, given that they are a wallet paying itself? Do you count raw addresses, or do you first group addresses that appear to share an owner? None of these has a wrong answer. They just produce different numbers.

Here is what those choices are worth, applied to the identical set of 4,329 transactions in block 963,218, mined 19 August 2026 at 20:15:57 UTC.

Same block, same arithmetic, answers ranging from 5,512 to 12,388. The definition decides the number before the data gets a say.

Why active addresses overstates the number of users

Almost every address is used once and thrown away

Of the 12,388 active addresses in block 963,218, exactly 11,760 appear in one transaction only. That is 94.93 percent. Just 628 addresses show up in more than one transaction in the entire block.

This is wallets working as designed, not users churning. Modern hierarchical deterministic wallets derive a fresh address for every incoming payment and a fresh change address for every outgoing one, because address reuse leaks your balance history to anyone who looks. Good privacy hygiene manufactures new addresses continuously, and the active address metric counts every one of them as a new participant.

Change outputs are counted as activity

Bitcoin spends whole outputs. A wallet holding one output of 1 BTC that wants to pay 0.1 BTC must spend the entire output and send roughly 0.9 BTC back to itself, at a brand new address. That change address did not receive a payment. It received its owner's own money back.

In block 963,218, 855 addresses both spent and received inside the same transaction, and 717 of those appeared nowhere else in the block. The classic single-input, two-output payment shape accounted for 2,709 of the 4,329 transactions, and 71.7 percent of all transactions had exactly two outputs, which is the signature of pay-plus-change.

One wallet tidying up can add hundreds of active addresses

The single largest transaction in the block, measured by addresses touched, pulled 293 inputs from 285 distinct addresses into one output. The whole thing was worth 0.15191017 BTC and it paid a 40,049 satoshi fee to move it.

That is one wallet sweeping accumulated dust into a single place. One owner, one economic decision, nobody paid. It contributed 285 active addresses, 2.3 percent of the entire block's count. A consolidation wave across a large custodian can move a daily active address figure noticeably while representing no change in demand whatsoever.

Exchange batching distorts it in the opposite direction

The same metric undercounts elsewhere. An exchange paying out 500 customer withdrawals does it in one transaction with 500 outputs, so 500 people become one sending entity. Worse, the overwhelming majority of exchange trading never touches the chain at all: it nets out inside the exchange's own database, and a million trades can settle as zero on-chain transactions.

So the metric inflates one user into many addresses, and compresses many users into one address, simultaneously. Which effect dominates depends on the mix of activity that day, which is exactly what you were trying to measure.

What entity-adjusted active addresses does about it

The standard correction is the common-input-ownership heuristic: if two addresses are spent together as inputs to the same transaction, the same party almost certainly controls both, because signing both required both private keys. Group addresses that way and you get an estimate of distinct actors rather than distinct addresses.

Applied inside block 963,218, that heuristic collapses 12,388 addresses into 9,789 actors, a 21 percent reduction. And that is a floor, not a final answer, because clustering within one block can only merge addresses that happened to co-spend in that same block. Running the heuristic across the full chain merges far more, since an address spent alongside another one last March is still the same owner today.

The heuristic has real limits and honest analysts state them. CoinJoin and PayJoin transactions deliberately combine inputs from different owners to break it, so clustering is inference rather than proof. It is still much closer to counting users than counting raw addresses is.

Why do active address numbers differ between providers?

Because each one made different, defensible choices at the four decision points above, on identical public data. One counts change, another strips it. One reports addresses, another reports entities. One counts an address that sent and received as a single participant, another counts it on both sides.

Anyone who has tried to reconcile two analytics dashboards and found two different user counts for the same week will recognize the pattern. Both pipelines are computed correctly. They are answering slightly different questions, and neither prints the question on the chart. The fix is the same in both worlds: pin down the definition first, then compare.

This is the same failure mode we found measuring on-chain volume, where raw output totals count change as if it were payment. If you want that one in detail, what on-chain transaction volume actually measures takes an earlier block apart the same way, and finds a single self-transfer accounting for 76 percent of the headline figure.

Is active addresses still a useful metric?

Yes, with its definition attached and used for the right job. It is a reasonable proxy for demand for block space and for how much the chain is being written to. Its trend over months is more informative than its level on any day, and comparing it against itself over a long window is far safer than comparing one provider's number against another's.

What it cannot do is tell you how many people used Bitcoin. No public chain metric can, because the data required is not on the chain. Treat it as a measure of ledger activity, which is what it honestly is, and it earns its place.

Does a fall in active addresses mean the price will fall?

That is not a question on-chain data settles, and we do not answer it. Active address counts move with wallet software defaults, exchange batching policy, consolidation waves during low-fee periods, and the steady migration of activity to off-chain and second-layer settlement. Any of those can move the series while demand is flat, and demand can move while the series is flat. This is informational data, not investment or trading advice.

Counting it yourself

Everything above came from public data. We pulled block 963,218 from a public Esplora index, paged through all 4,329 transactions, and counted addresses in Python. That is completely workable for one block. It stops being workable the moment you want a daily series, because you are then fetching every transaction of every block since 2009 and maintaining the address index yourself.

That is the work an indexed chain has already done. On BitcoinDatabase, Bitcoin active address data comes back as a series with each definition available separately, so you can read raw unique addresses and entity-adjusted counts next to each other instead of picking one blind. The clustering behind the adjusted figure is documented on our address clustering page, the wider metric set lives under on-chain metrics, and if you would rather define the metric yourself, the whole chain is queryable in SQL so you can write your own version and compare it against ours.

For address-level work rather than aggregates, the wallet tracker follows a set of addresses over time with change and self-transfers separated out, and the rich list shows why address counts and holder counts are not the same thing at the top of the distribution either.

All figures in this article were measured on 19 August 2026 from block 963,218, hash 000000000000000000007a2e4d7c4ae9b0d183dd9fd61cce08b56f6dc70c75e1, mined at 20:15:57 UTC with 4,329 transactions. Every number is reproducible from the public chain. This is informational on-chain data only, not financial, investment or trading advice.