Dappradar
DappRadar rankings compared dapps through tracked wallet activity
DappRadar rankings compared decentralized applications using unique active wallets, with other metrics showing transaction activity and asset value. A higher wallet count meant more distinct addresses interacted with the tracked contracts during the selected period. It did not establish a larger human audience or better investment performance. Meaningful comparisons keep the category, blockchain coverage, dates, and sorting metric consistent. Historical tables remain useful for those comparisons, although the original operator announced a wind-down in November 2025. Reading a saved ranking therefore involves both understanding its measurements and keeping its conclusions tied to the activity period that it actually covers.
- updatedHistorical wallet rankings support meaningful comparisons when the applications share measurement periods, contract coverage, and sorting criteria.
Sorting Metric and Comparison Group
A ranking position expresses a dapp's place within a particular group ordered by a particular measurement. The original general rankings supported category and blockchain filters, alongside sorting by users, volume, or balance. Choosing a smaller comparison group changes which applications compete for the same positions.
For wallet comparisons, the relevant column is unique active wallets, usually shortened to UAW. Record whether the order runs from largest to smallest or the reverse. An application near the top of a category need not occupy the same position across all categories. Neither position is inherently contradictory: each answers a different comparison question.
Historical Tables and Service Continuity
The original platform's operator began winding down its platform and associated operations in November 2025. Accessible pages alone do not establish continuity of the original tracking service. A historical ranking can support a dated comparison without establishing which application leads today. Keep the observation period attached to any saved result, particularly when an older explanation appears under a newer page-update label.
Matched Periods and Percentage Changes
Comparable wallet totals need matching measurement intervals, while growth comparisons also require the same basis for the earlier period.
Observation Windows
The original general rankings offered 24-hour, seven-day, and 30-day views. These windows answered different questions about activity. A short interval emphasized recent participation; a longer interval included wallets that interacted less frequently. Those historical options do not establish which controls a later interface supports.
Equal duration is only part of the comparison. Different end dates can include different campaigns or activity bursts. Keep both boundaries when the dataset supplies them, especially when comparing a saved table with another capture.
Growth Against a Baseline
For a positive earlier count, percentage growth equals the change in wallets divided by that earlier count, multiplied by 100. The calculation describes a relative change. A large percentage can arise from a small initial count, so it does not establish a large audience.
Absolute wallet totals and percentage changes answer different questions. Use the total to compare recorded scale within the period. Use the change to describe movement against the stated baseline, without treating the fastest-growing entry as the largest.
Distinct Wallets and Repeat Activity
UAW measures the breadth of recorded wallet participation, while transactions describe how many interactions the tracked activity contains. UAW counts distinct wallet addresses interacting with a dapp's tracked smart contracts within the measurement period. Repeated qualifying interactions from the same address do not create additional unique addresses in that period.
Transaction count divided by UAW gives an aggregate transactions-per-wallet ratio when both figures cover the same activity. It does not reveal the distribution across individual wallets. A few highly active addresses can affect the ratio, and the average does not describe every participant. Keep the underlying counts beside the calculation so that repeated activity remains distinct from wider participation.
What Can a Higher UAW Position Establish?
A higher position in a descending UAW table establishes more recorded active addresses than lower entries with smaller counts. The conclusion applies to that table's coverage and dates. One person can control several addresses, and activity outside tracked blockchain interactions can escape the measurement. A ranking therefore supports an address-activity comparison; it cannot identify the number of people behind those addresses or measure contract security.
Contract Coverage and Missing Activity
Contract coverage determines which interactions contribute to an application's measured activity, so differences in coverage affect the apparent comparison.
Included Contracts
DappRadar's original measurements relied on contracts associated with each application, including contract information supplied by developers. An application can use several contracts for different functions. Measurements covering only part of that set can omit activity that belongs to the broader application.
A change in the tracked set can also change the count without an equivalent change in audience behavior. A jump around a coverage change deserves a different interpretation from growth measured under an unchanged definition.
Activity Outside the Measured Set
Applications differ in how much work they perform on a blockchain. Some record frequent user actions through contracts. Others keep substantial activity in software outside the blockchain and only record selected asset interactions. The same UAW figure can therefore represent different proportions of total application use.
A missing figure does not establish an empty activity set. Distinguish an explicit zero for a defined interval from unavailable data. Where coverage remains unclear, the comparison cannot establish which application had more total activity.
Volume and Balance Beside Wallet Counts
Volume and balance add information about asset value that wallet counts alone cannot provide, but each measures a different quantity. The original rankings defined volume through token value moving into and out of tracked contracts. Balance described the value held in those contracts.
Volume concerns movement over an interval; balance concerns holdings at a point in time. Higher volume with fewer active wallets implies more transferred value per active address when the compared figures share coverage and the same measurement period. It does not establish higher profits. Changes in token valuations can also affect monetary totals without a matching change in the number of participating addresses.
A Worked Comparison of Two Saved Rows
Consider hypothetical saved rows for two unnamed dapps with the same category, network coverage, observation dates, and complete measurements. Every count in this example is hypothetical. The first row contains 1,432 UAW and 4,296 transactions. The second contains 1,197 UAW and 5,985 transactions. Assume that each transaction total and wallet total cover the same qualifying activity.
Order the rows by descending UAW. The first dapp ranks above the second because it has 235 more active addresses. Divide transactions by wallets: 4,296 divided by 1,432 equals three, while 5,985 divided by 1,197 equals five. The second row has more transactions per active wallet despite its lower UAW position.
The saved counts reproduce the UAW order and both aggregate ratios. They establish neither more human users nor a lower cost of using either application.
Transaction counts alone cannot supply a fee estimate. Where execution incurs gas charges, the operations performed and the applicable fee rate affect the cost. A count does not contain those inputs, and any application charges require separate consideration.
If the second row actually covers a different interval, the arithmetic remains correct but the comparison loses its common basis. Replace that row with a matching observation before drawing the comparative conclusion. If no matching observation exists, retain the individual figures and leave their relative activity unresolved.
Campaign Spikes and Automated Activity
A sudden rise in wallet activity can reflect an event or incentive rather than sustained participation across later periods. Aggregate totals do not reveal motivation. Automated addresses can also interact with contracts and contribute to recorded activity.
Relationships between UAW and transactions can identify patterns worth examining, but a particular ratio does not prove automation. An application that requires infrequent transactions can produce a different pattern from one that records frequent actions. Later observations help distinguish a brief concentration of activity from persistence, although persistence alone still does not identify unique people.
Category-Specific Meaning
Category comparisons work best when the applications use blockchain interactions for similar functions, even if their interfaces look different. A game can record asset activity while keeping gameplay elsewhere. A financial application can generate transactions through deposits, withdrawals, and exchanges. Those actions represent different kinds of participation.
The original rankings introduced category-specific metrics to make these differences more visible. Preserve that distinction when interpreting a saved table. An NFT trading measurement and a general dapp wallet measurement need not count the same actions, even when they describe related products.
Ranking Tables and Transaction-Level Analysis
Ranking tables answer relative activity questions efficiently because they place comparable aggregate figures beside one another. Their limits appear when the question concerns individual behavior: whether the same addresses returned, which operations they performed, or how activity clustered across wallets.
Those questions require records beneath the totals and a defined method for analyzing them. A table is sufficient for establishing which recorded count is larger. Transaction-level analysis supports narrower questions about the interactions behind that count, while still requiring care before attributing several addresses to a single person.
Everyday questions about Dappradar rankings
Can Identical UAW Totals Justify Different Ranking Positions?
Identical exact UAW totals do not establish a difference in wallet activity. A displayed order may use another sorting field or a tie-breaking rule, but the row positions alone do not identify that rule. Treat equal exact counts as equal on this metric unless the table explains another distinction.
How Should Rounded Wallet Counts Be Compared?
Rounded wallet counts can conceal differences between the underlying totals. Matching abbreviated values therefore do not prove that two dapps recorded identical UAW. Use unrounded figures when available; otherwise, describe the displayed values at their stated precision and avoid calculating an exact gap from them.
Does a dapp's Share of Summed UAW Represent Its Share of Unique Users?
A share of summed UAW does not represent a share of unique people. The same address can interact with several dapps, so adding application totals can count that address repeatedly. Such a fraction describes a share of summed application-level counts within the selected dataset, with overlapping participation.
What Happens to Percentage Growth When the Previous Wallet Count Was Zero?
The ordinary percentage-growth formula is undefined when the previous wallet count was zero because it requires division by that count. Describe the absolute increase or the transition from no recorded wallets to recorded activity. A display convention does not turn that transition into a finite, comparable growth percentage.