Active addresses count blockchain addresses that took part in successful transactions during a selected period, usually as a sender or recipient. Holders count addresses with a nonzero balanc
Active addresses count blockchain addresses that took part in successful transactions during a selected period, usually as a sender or recipient. Holders count addresses with a nonzero balance of a particular token. The first is a measure of observed activity over time; the second is a snapshot of addresses retaining an asset.
Neither figure is a people count. A participant can use several wallets, while one address at an exchange, custodian or protocol can stand in for many customers, assets or functions. The useful question is therefore not which metric is “the” adoption number, but what each says about participation and ownership when read alongside other on-chain evidence.
Active-address data begins with transactions. Coin Metrics’ documentation describes active addresses as unique addresses participating in successful transactions within a defined interval, typically as senders or recipients. That interval might be a day, week or month, and the choice materially changes the result.
An address that sends tokens twice during one daily window normally contributes one unique address to that day’s count, not two. An address that receives tokens also qualifies under the sender-or-recipient approach. The metric therefore removes repeated appearances by the same address within the selected period, but it does not identify the person or organisation behind that address.
Methodology can differ among data providers. Glassnode, for example, defines active addresses as unique senders or receivers, while an expanded version includes addresses that called smart contracts. That distinction matters for networks and tokens where users interact principally with decentralised applications rather than making simple transfers.
Before comparing two active-address charts, establish what counts as activity: successful transfers only, or transfers plus contract calls; token-level activity, or activity on the underlying chain; and which measurement window is in use. Similar labels do not guarantee comparable series.
A holder count starts from ownership records rather than a period of transaction activity. For an ERC-20 token, the usual approach is to identify every address with a balance greater than zero at a particular point in time. The ERC-20 standard exposes balances through balanceOf and defines total token issuance through totalSupply, providing the basic information used to construct such a count.
This makes holders a stock metric. It answers: how many addresses currently retain some amount of the token? Active addresses are a flow-like activity metric. They answer: how many distinct addresses participated during this interval?
The difference is practical. An address can hold a token throughout a month and never transact, adding to the holder total but not the month’s active-address figure. Conversely, an address can receive and later send a token during a day, contributing to activity even if it ends the day with no balance and is absent from an end-of-day holder snapshot.
The raw total makes no distinction between an address holding a minimal amount and one holding a large allocation; each adds one as long as its balance is nonzero. That limits what holder growth can show: without additional evidence, it should not be read as a measure of capital committed, distribution quality or recurring use.
The central limitation applies to both measures: addresses are technical identifiers, not verified identities. On Ethereum, an address can represent either an externally owned account or a smart contract, as Ethereum.org’s account documentation explains. Raw counts can consequently include exchange wallets, custodial addresses, bridges, protocol contracts, treasuries and other contracts.
That creates distortion in both directions. One investor or trader may deliberately separate activity across several wallets, increasing the apparent number of holders or active addresses. At the other extreme, a single exchange or custodian address may aggregate balances or transactions for many underlying customers, reducing the number of addresses visible on-chain relative to the number of people involved.
Smart contracts complicate the picture further. A contract can hold tokens because it is a pool, vault, bridge endpoint or other application component. It may also be active because it receives a transfer or is involved in an interaction counted under a provider’s methodology. Its appearance is real on-chain activity, but it is not automatically evidence of one additional human user.
Entity-adjusted analytics attempt to group addresses believed to belong to the same broader entity. This can make a dataset more useful for certain questions, but the groupings remain estimates rather than a complete identity registry, according to Glassnode’s guide to entity-adjusted metrics. Raw-address and entity-adjusted figures should therefore not be treated as interchangeable.
Tokenised vaults offer a useful example of why a holder count needs structural context. Under ERC-4626, vault shares represent claims on underlying assets. A wallet holding vault shares is not simply holding an unrelated token balance; it has a claim governed by the vault’s share and asset mechanics.
Consider a simplified sequence. A participant deposits an underlying asset into a vault and receives shares. The participant’s address can become a holder of the vault-share token. The vault contract holds or manages the underlying asset, and that contract may itself appear as a significant holder or as an active address in data associated with the relevant tokens.
Reading the resulting charts requires separating these roles. An increase in share holders may show that more addresses hold claims on the vault, but it does not establish how many distinct people are involved. Activity may reflect deposits, withdrawals, transfers of shares, or contract interactions, depending on the dataset’s definition. A large contract balance can be a normal feature of the product’s design, rather than evidence that a single investor dominates the economic exposure.
The same discipline applies beyond vaults. Before interpreting a top-holder list or an activity spike, identify whether prominent addresses are wallets, contracts, custodians or labelled infrastructure. Token design determines what a balance represents and what an interaction means.
The two metrics become most informative when they diverge. Rising holders alongside low active-address rates can be consistent with passive ownership or distribution campaigns. Rising active addresses while holder counts remain broadly flat can be consistent with more frequent use by an existing address base. Those are possible readings, not proof of motive, user growth or product-market fit.
A disciplined review adds context before drawing a conclusion. Glassnode’s activity guide recommends considering transfer volume, retention, concentration, contract labels and the measurement window alongside address metrics.
It is also worth keeping the unit of analysis explicit. A chain-wide active-address figure does not necessarily describe activity in one token, while a token’s holder count does not reveal whether its holders are active elsewhere on the chain. A provider’s methodology, the token’s architecture and the addresses included all set the boundaries of the claim.
In practice, holder counts are best used to describe the breadth of visible nonzero ownership, and active addresses to describe visible transaction participation during a specified period. The gap between them is often the point worth investigating, especially where intermediaries and contracts can aggregate or multiply the addresses seen on-chain.
No. They count unique addresses meeting a transaction-based definition during a selected window. One person can control multiple addresses, and one address can represent a custodian, exchange or contract serving many people or functions.
More addresses with nonzero balances, by themselves, do not establish the number of people involved, the size of those balances or whether the token is being used.
Some datasets include contract callers in an expanded active-address definition. This can better capture application interaction, but it also means the series may not match a transfer-only active-address metric.
An exchange may use one or a small number of on-chain addresses for many customers. Those addresses can mask a large underlying customer base, while users who withdraw to several self-controlled wallets can have the opposite effect on raw counts.
Review transfer volume, retention, balance concentration, known contract or entity labels, and the time window used. These checks help determine whether a change is more consistent with holding patterns, repeated activity, infrastructure movements or a shift in methodology.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
