Key Takeaways
- What it is: The count of distinct addresses participating in qualifying ledger activity during a defined period.
- How it is built: Providers count unique sending addresses, receiving addresses, or both, often with network-specific rules for contracts, failed transactions, and zero-value activity.
- Core expression: Active addresses = count of distinct qualifying addresses observed as sender or recipient during the interval.
- Best use: The metric is a participation proxy, not a user count. Trends can indicate changing network interaction when methodology remains stable.
- Main limitation: One user can control many addresses; one exchange address can represent many users; contracts and bots inflate activity; address formats differ by network.
- Practical rule: Before trusting an active-address trend, check whether contract calls and bot addresses are included or excluded, and whether exchange or protocol addresses are being counted as if they were individual users.
Who This Guide Is For
Active addresses is the most cited and most misread on-chain metric, because it looks like a user count and is not one. Read this page if you have seen an active-address chart used as evidence of adoption and want to know what the number can and cannot support.
The construction section matters most for anyone comparing two chains, since the word address means a different object on a UTXO chain than on an account chain. Engineers should note the sender, receiver, and union definitions, which produce materially different series from the same blocks.
Educational content. Not individualized financial advice.
What Does Active Addresses Measure?
Active addresses counts how many distinct addresses appeared in qualifying ledger activity during a period. It is a measure of address participation. The distance between address participation and user participation is large, runs in both directions, and does not cancel out.
In one direction, a single person routinely controls many addresses. Hierarchical deterministic wallets generate a fresh receiving address for every incoming payment by design, precisely so that observers cannot link them, and a user who receives ten payments has produced ten addresses. In the other direction, a single exchange hot wallet address can process activity on behalf of millions of customers and counts as exactly one.
Plain-language definition
Active addresses is the number of distinct addresses that sent or received value in a period. It is a headcount of addresses, not of people.
Technical definition
Let S be the set of addresses in a sending position and R the set in a receiving position across all qualifying transactions in the interval. Providers publish |S|, |R|, or |S ∪ R| depending on the definition chosen. The union is most common and is roughly double the sending-only count on most chains, which is why comparing two providers without checking this first produces spurious differences.
How Is Active Addresses Constructed?
The address object itself differs by ledger model, which is the first thing to establish before any cross-chain comparison.
- UTXO chains. An address is a pattern encoded in an output script. It has no ledger existence of its own; it exists only as a spending condition attached to outputs. Counting addresses means counting distinct script patterns observed, and the same wallet deliberately produces new ones.
- Account chains. An address is a first-class account with persistent state. Contract accounts share the address space with externally owned accounts, so a naive count includes every contract touched.
Build steps
- Select qualifying transactions. Decide whether failed transactions count, which matters on account chains where a reverted transaction still consumed gas and still names a sender.
- Extract addresses in sending and receiving positions.
- Decide contract handling. Counting contract addresses on a chain with heavy DeFi activity can dominate the series and is not comparable to a chain without contracts.
- Decide zero-value handling. Zero-value transfers cost gas but move nothing and are a known spam vector.
- Deduplicate within the interval and count.
Why the count is not additive across days
Weekly active addresses is not the sum of seven daily counts, because an address active on multiple days is deduplicated only within each interval. A provider publishing a weekly series computed as a sum rather than a distinct count over the week is publishing a different quantity, and the gap between them is itself a rough measure of repeat activity.
Formula and Measurement Logic
Active addresses = |{addresses observed as sender or recipient in qualifying transactions during the interval}|
The formula is a set cardinality, so the only real decisions are what goes into the set. Those decisions are listed below and each one changes the answer by a large factor rather than a small one.
| Decision | Options | Typical magnitude of effect |
|---|---|---|
| Position counted | Sender only, receiver only, or union | Union is roughly twice sender-only on most chains |
| Contract addresses | Included or excluded | Large on contract-heavy chains, nil on Bitcoin |
| Failed transactions | Counted or dropped | Matters on account chains during congestion |
| Zero-value transfers | Counted or dropped | Can be dominant during spam campaigns |
| Interval | Daily, weekly, monthly distinct count | Not additive; longer intervals dilute repeat users |
| Change addresses | Counted as receivers or stripped | Inflates UTXO chain receiver counts |
There is no normalization step in the formula, and that absence is itself a limitation. A raw count grows with the chain and cannot be compared across chains of different sizes without dividing by something, most usefully transaction count or supply.
How Should Active Addresses Be Interpreted?
The defensible reading is narrow: within one chain, under one unchanged definition, the direction and rate of change in address participation. Everything beyond that requires additional evidence.
What the number cannot tell you
- How many people used the network. Address rotation and custodial aggregation break the mapping in both directions and neither effect is measurable from the count.
- Whether usage is economically meaningful. An address that received a dust spam transfer counts identically to one that settled a large payment.
- Whether growth is organic. Airdrop farming produces enormous address creation with a single beneficiary behind it, and this is a deliberate, well-understood strategy rather than an edge case.
What makes the number more useful
Ratios rescue it. Active addresses divided by transaction count indicates whether activity is spread across many participants or concentrated in a few doing a lot. New addresses as a share of active addresses separates first-time participation from repeat participation. Both are computed from series this page and its siblings cover, and both are more robust than the raw count because the definitional quirks partly cancel in the numerator and denominator.
Step-by-Step Workflow
- Establish whether the series counts senders, receivers, or the union.
- Establish whether contract addresses are included, and on a contract-heavy chain, get the series both ways.
- Confirm the interval is a distinct count over the interval, not a sum of daily counts.
- Check for a coincident airdrop, incentive program, or points campaign on the chain before attributing growth to adoption.
- Divide by transaction count to see whether participation is broadening or concentrating.
- Pull new addresses separately to separate first-time from returning participation.
- Describe the result as address activity, never as user growth, unless clustering evidence supports the stronger claim.
Worked Hypothetical Scenario
Two chains each report 500,000 daily active addresses. That equality is where analysis usually stops, so work out what it can conceal.
| Chain A | Chain B | |
|---|---|---|
| Active addresses | 500,000 | 500,000 |
| Transactions | 350,000 | 4,000,000 |
| Addresses per transaction | 1.43 | 0.125 |
| New addresses | 420,000 | 25,000 |
| New as share of active | 84% | 5% |
Chain A shows more addresses than transactions and 84 percent of them appearing for the first time. That pattern is what an airdrop farming campaign looks like: addresses created to qualify, used once, and abandoned.
Chain B shows eight transactions per active address and almost no new addresses. That pattern is a smaller set of participants transacting repeatedly, which could be genuine heavy usage or a handful of automated systems.
Neither chain's headline number was wrong, and neither supports the adoption claim usually made from it. The two ratios did all the work, and both are computable from series most providers already publish.
What Can Make the Interpretation Wrong?
- Reading it as a user count. The central error. Wallets create addresses per payment by design and custodians aggregate millions of users behind one.
- Incentive-driven inflation. Airdrop and points campaigns reward address creation directly. Growth during such a campaign measures the campaign.
- Contract addresses on account chains. Including them makes a DeFi chain look far more populated and destroys comparability with a chain that has none.
- Definition mismatch between providers. Sender-only versus union roughly doubles the figure. Two charts that appear to disagree often just count different sets.
- Interval arithmetic. Weekly is not the sum of daily. Series built that way overstate and drift.
- Layer-2 migration. Activity moving to a rollup leaves the base-layer address count, which reads as declining adoption while total usage rises.
- Dust spam. Sending tiny amounts to many addresses manufactures active receivers at low cost.
Cross-Network and Provider Comparison
Cross-chain comparison of raw active addresses is the weakest common use of this metric, because the counted object is not the same thing.
On Bitcoin, addresses are ephemeral script patterns and privacy-conscious wallet software maximizes the number generated. On Ethereum and similar account chains, addresses are persistent accounts with balances, reuse is normal, and contract accounts occupy the same namespace. The same underlying level of human activity therefore produces systematically more addresses on the UTXO chain and systematically fewer on the account chain.
Rollups add a third case. An address active on a rollup is invisible in base-layer counts, so a chain whose ecosystem has migrated to layer 2 shows base-layer address decline that is a migration, not a contraction. Any comparison spanning a chain with an active rollup ecosystem and one without needs to state which layers are included.
Chains with cheap or subsidized transactions face far more address spam than chains where a transaction costs a meaningful amount, so fee level is a confounder in every cross-chain address comparison.
Advanced Analytical Methods
Entity clustering
Applying heuristics such as common-input ownership on UTXO chains collapses addresses controlled by the same actor into one entity, converting the metric from address participation toward something nearer to participant participation. The heuristics are imperfect, defeated by design in some wallet software, and produce labels that change retroactively when the clustering is updated.
Activity ratios
Active addresses over transaction count, and new over active, are both more robust than the raw series because definitional quirks partly cancel between numerator and denominator. These two ratios distinguish broadening participation from concentrating participation and first-time from returning activity.
Economic filtering
Restricting the count to addresses transacting above a value floor removes dust spam and airdrop farming at the cost of introducing a threshold that must be justified and disclosed.
Cohort retention
Following addresses first active in one period and measuring how many return separates durable participation from single-use address creation, which is the specific failure this metric is most vulnerable to.
Swoopr Investment Tool
Recommended tool: Active Address Decomposition chart separating senders, receivers, contracts, funded accounts, and entity-adjusted activity.
Inputs should include network, asset representation, provider, interval, entity treatment, price source, filters, and baseline. Outputs should expose the definition, formula or query logic, source timestamp, methodology version, alternatives, exclusions, sensitivity, related guides, and a saveable research note. The proposed interface must expose the page-specific construction: providers count unique sending addresses, receiving addresses, or both, often with network-specific rules for contracts, failed transactions, and zero-value activity.
Any tool built from this concept would stay descriptive, not advisory, it would never label an asset a buy, a sell, safe, guaranteed, or certain. It would also flag clearly when data is unavailable, delayed, unsupported for a given network, or conflicting across providers, rather than presenting an uncertain reading as fact.
Practical Checklist
- I know whether this series counts senders, receivers, or the union.
- I know whether contract addresses are included.
- I confirmed the interval is a distinct count, not a sum of daily counts.
- I checked for a coincident airdrop or points campaign.
- I computed active addresses over transaction count.
- I checked new addresses as a share of active addresses.
- I accounted for layer-2 migration if the chain has rollups.
- I described the result as address activity rather than user growth.
Frequently Asked Questions
Is one active address the same as one user?
No, and the error runs in both directions. Hierarchical deterministic wallets generate a fresh receiving address for every incoming payment by design, so one person produces many addresses. A single exchange hot wallet address can process activity for millions of customers and counts as one. Neither effect is measurable from the count itself.
Why do two providers report different active address counts?
Most often because one counts only sending addresses and the other counts the union of senders and receivers, which is roughly double on most chains. The other common cause is contract address handling on account chains. Establish both definitions before treating a difference as a data problem.
Is weekly active addresses the sum of seven daily counts?
No. Addresses are deduplicated within each interval, so an address active on three days counts once in the weekly distinct count and three times in a sum. A series built by summing daily counts is a different quantity and drifts upward relative to the correct one.
How do airdrops distort active addresses?
Airdrop and points campaigns reward address creation directly, so participants generate large numbers of addresses to qualify. Growth during such a campaign measures the campaign rather than adoption. Checking new addresses as a share of active addresses exposes this pattern quickly.
Why does base-layer active addresses fall when a chain gains rollups?
An address active on a rollup does not appear in base-layer counts. A chain whose ecosystem migrates to layer 2 therefore shows base-layer decline while total usage rises. Any comparison spanning a chain with an active rollup ecosystem must state which layers are included.
Should contract addresses be counted as active?
It depends on the question, but the choice must be disclosed because it is not a small adjustment. On a contract-heavy chain, including contract addresses can dominate the series and destroys comparability with a chain that has no contracts at all.
What is more useful than the raw active address count?
Two ratios. Active addresses divided by transaction count shows whether activity is spread across many participants or concentrated in a few doing a lot. New addresses as a share of active addresses separates first-time from repeat participation. Both are more robust than the raw count because definitional quirks partly cancel between numerator and denominator.
Does an address count as active when it receives, or only when it sends?
Providers differ, and the choice changes the series materially. Counting only senders measures parties that took an action, since sending requires a key. Counting receivers as well includes addresses that were passive recipients, which inflates counts on any day involving a distribution to many addresses. Some providers count both and deduplicate, some count each side separately. Because an airdrop or a large payout creates enormous numbers of receiving addresses and almost no sending ones, the definition determines whether such an event registers at all.
Why does an active address series usually show a weekly cycle?
Because a large share of on-chain activity is connected to businesses and to fiat rails that follow a working week. Exchange operations, settlement processes, payroll-like flows and institutional activity cluster on weekdays, so weekend counts run lower even though the chain itself does not stop. The practical consequence is that comparing a Saturday with the preceding Wednesday measures the day of the week rather than a change in usage, which is why these series are usually read as seven-day averages.
References
These sources should be reviewed during editorial verification. They support data structures and methods, not the hypothetical conclusion. Provider formulas, chain rules, and APIs can change. Confirm current documentation before publication.
- Ethereum.org: Transactions: Ethereum transaction fields and execution.
- Ethereum.org: Gas and Fees: Gas, base fees, tips, and block-space demand.
- Bitcoin Developer Guide: Transactions: UTXO transaction construction and spending.
- Coin Metrics: Transaction Metrics: Transaction-count definitions.
- Coin Metrics: New Addresses: New and funded address methodology.
- Coin Metrics: Network Data Glossary: Cross-network address, account, ledger, and UTXO definitions.
- Dune: Data Explorer and Raw Tables: Blocks, transactions, logs, traces, and decoded data.
- Dune: Curated Data Overview: Cross-chain normalized datasets. Editorial review for active addresses should confirm that every provider definition remains current on the publication date.