Could the same wallet contribute to several dapps' UAW totals?

The same wallet could contribute to separate dapp-level UAW figures through interactions with each application's tracked contracts. Those counts described participation in different applications. Adding them would not establish the number of distinct wallets across the combined group, because the same address could occur in more than one total.

Which general-ranking filters required PRO to work together?

The historical general-ranking interface reserved combined Balance, Users and Volume range filters for PRO members. Individual metric-range filtering was available more broadly. That distinction concerned simultaneous filter combinations, rather than a different definition of the underlying data. It describes the original interface, not a current membership offer.

Was an NFT collection's floor price its average sale price?

An NFT collection's floor price was its lowest listed asking price, while its average sale price summarized NFTs sold during a reporting period. These figures could move differently. Average price reflected completed sales, so it did not describe the value of every NFT in the collection.

Did Hot Contracts show dapps absent from the general rankings?

The historical Hot Contracts feature could surface active contracts from dapps not yet listed in the directory. Its unit of comparison was the smart contract, whereas a general-ranking entry represented a listed dapp. A trending contract therefore did not necessarily have a corresponding application-level ranking.

How did the activity sparkline differ from a rank history?

The activity sparkline plotted changes in the metric selected for the ranking, rather than changes in the position number. A UAW-sorted view showed wallet activity across its selected window. A Balance view showed changes in holdings, so an upward line did not by itself establish an improvement in relative rank.

What did the new-dapp filter select?

The new-dapp filter selected recently listed applications within the historical rankings. Under the developer plans described in May 2025, new Basic listings kept the 'new' badge for 7 days and new Premium listings for 14 days. The filter distinguished additions to the directory from the wider set of tracked dapps; it did not change the definitions of UAW, Volume or Balance.

Could the API return transaction counts for top-ranked dapps?

The original API's top-dapp data included transaction counts alongside UAW and volume. That provided an additional activity measure beyond the general table's documented sorting choices. These fields describe historical data access and do not establish that the original endpoints remain available after the platform's wind-down.

Does a high Volume figure mean a dapp earned high revenue?

A high Volume figure measures asset flows through tracked contracts and does not establish high revenue. Transferred assets can belong to the people interacting with an application. Establishing revenue requires distinguishing income the application earns from the total value passing through its contracts.

Dappradar rankings sorted tracked dapps by on-chain activity and asset value

Dappradar rankings ordered tracked decentralized applications, or dapps, by wallet activity, token volume and contract balances. Each position depended on the selected metric, comparison group and observation period. The general rankings offered 24-hour, 7-day and 30-day views, alongside specialist DeFi and NFT rankings. Unique Active Wallets (UAW) measured participating addresses, so a wallet-based position did not establish a count of individual people. The original platform announced a wind-down in November 2025. A May 2026 update described a transfer of platform assets to new ownership. Historical positions therefore need the measurement definitions and filters which produced the original comparison.

Updated Sunday 11 October 2026

In short: A historical dapp position is meaningful only alongside its sorting metric, observation period and tracked contract coverage.

Contract activity and filters set the comparison

Tracked smart contracts supplied the measurements, while category and blockchain filters determined which dapps appeared together. Product-level records connected those contracts to an application. A product could span multiple blockchain ecosystems, with chain-specific views showing different portions of its activity. Category choices included games, DeFi, exchanges, collectibles, marketplaces and social applications. Dapp discovery brought descriptions alongside measured usage, but the numerical position came from the selected metric. Because a category filter changed the comparison group without changing what a wallet count or asset value meant, a leading position within one category did not establish leadership across the complete directory of tracked applications.

The general rankings allowed sorting Balance, Users and Volume from high to low or low to high. The Users label referred to UAW. Value-range filters further restricted which entries remained in a comparison. Reading a saved table requires those settings: the first visible entry under ascending sorting represented the smallest selected value.

Choose the measure behind the position

Each measure answered a different question about activity or capital within its tracked contract scope. UAW concerned participating addresses. Transactions counted recorded interactions and added context about how much activity those addresses generated. A transaction count belonged to the product's analytics; the documented general-table sorting choices centered on UAW, Volume and Balance. Volume described the US dollar value passing through monitored contracts, whereas Balance described the US dollar value held there. These measures could produce different leaders because they measured different properties of the same application.

Ranking measure	What it compared	Measurement boundary
General UAW	Distinct active wallet addresses	Tracked contract interactions within the selected period
General Volume	Value of token flows through contracts	Transfers involving monitored contracts
General Balance	Value of assets held in contracts	A snapshot of monitored holdings
DeFi TVL	Total value locked in DeFi contracts	Tracked locked assets and their valuation
Positions remain comparable when the measure, contract scope and observation basis match.

The DeFi TVL view addressed locked capital, adding a specialist comparison beside the general sorting options. TVL meant Total Value Locked. Choosing between these views depended on the question: breadth of on-chain participation, asset movement or holdings at an observation point.

Time windows and trendlines gave positions context

The general rankings used different reporting windows, with activity lines showing changes inside the selected period.

The 24-hour view

A 24-hour activity figure described a short observation window. It could reflect concentrated activity without establishing persistence across a longer period. Comparing that figure with a 7-day total changed the measurement basis, even when the dapp name and column label matched. A larger total over a longer window alone did not demonstrate faster growth.

Open full-size image

Timing also affected what a saved ranking captured. The reporting window and the moment of observation both mattered. Tables recorded at different moments could cover different activity, so their positions were not interchangeable simply because both carried a 24-hour label.

The 7-day and 30-day views

Longer views extended the period used to examine wallet activity and token flows. They could reveal activity which a short window missed. In particular, a period-wide wallet count did not measure newly acquired people or prove sustained participation by every address.

The Balance figure represented a snapshot rather than a cumulative total for the selected period. Its activity line showed how holdings changed during that window. Summing successive balances would repeatedly count assets which remained in the contracts. Balance therefore required a point-in-time comparison, even when a chart supplied historical context.

A position moved with its comparison group

A rank described relative order, so movement depended on other entries as well as the selected dapp. An application could lose places while its measured activity increased if competing entries increased more. Category filters and value ranges could also change the visible order. Comparisons of rank movement therefore required matching groups and sorting directions, with the underlying values explaining what actually changed.

Specialist rankings compared DeFi capital, NFTs and community support

DeFi, NFT and community rankings used different measures or objects, so their leading positions answered different questions.

DeFi capital

DeFi rankings included TVL and Adjusted TVL (aTVL), with token valuation affecting their relationship. Nominal TVL changed with both token quantities and token prices. Adjusted TVL held prices fixed at the start of its measurement period. This made changes in tracked locked assets easier to distinguish from market-price changes. Market-cap fields and market-cap-to-TVL ratios added token-valuation context to the capital comparison.

NFT collections and sales

NFT rankings separated collections, individual sales, marketplaces and fractional NFTs. Collection statistics described trading across a group of assets; an individual-sale ranking concerned a particular transaction. Marketplace rankings concerned activity at the trading venue. Fractional NFT rankings concerned assets whose ownership involved multiple token holders. The general Collectibles category instead described interactions with the collectible project's dapp. Its UAW position therefore answered a different question from the collection's NFT sales volume.

Community support

Under the July 2025 boosting rules, Boosted Rankings ordered eligible listed projects by allocated Boosting Power, with a 1.8x multiplier for Premium dapps. High-Risk dapps could not receive boosts, and a cycle's top three projects could not receive boosts in the following cycle. That measure expressed support within a two-week cycle, after which allocated Boosting Power reset. It differed from the general rankings' recorded wallet activity and token flows. A high boosted position therefore needed its own interpretation and could not establish leadership on an on-chain metric.

Did a higher position always mean greater adoption?

No, a higher position described the selected measure and did not establish a complete adoption count. Address-based rankings reflected wallets interacting with tracked contracts. A person could operate several wallets, while activity outside the blockchain could leave no corresponding transaction. These differences affected the relationship between a UAW position and the application's actual audience.

Repeated interactions could increase transaction counts without increasing distinct wallet participation proportionally. Automated systems also generated genuine blockchain activity. Their transactions could serve a trading function, so automation alone did not establish fraudulent use.

A consistent ratio of transactions to UAW over time could justify closer examination, but it did not prove bot activity. The application's mechanics affected how many transactions participation required. A ranking supplied an activity measure; it did not identify the intention behind each interaction or distinguish every automated address from a person.

Contract coverage set another boundary. Omitting a relevant contract left its activity outside the monitored figures. Adding contracts could change reported measurements without representing an equivalent change in underlying demand. Historical comparisons therefore needed consistent coverage, especially when the same product name concealed a change in what the platform tracked.

Dappradar rankings: Did a higher position always mean greater adoption?

Open full-size image

Historical rankings and the ownership change

The original platform began winding down in November 2025, limiting present-day interpretations of its historical rankings. On 13 May 2026, an update described new ownership for the brand and platform assets. The transition excluded the DAO and RADAR token. These changes separated the historical measurement system from assumptions about later services, memberships or token-based access.

The original API also exposed top-dapp activity data, extending analysis beyond the visible rankings table. Saved API records and ranking tables describe the periods they captured, so a later service changing its metrics or contract coverage cannot automatically supply positions which form a continuous series with the original rankings.

Illustration: Dappradar rankings: Historical rankings and the ownership change

Open full-size image

Dappradar rankings FAQs

Could the same wallet contribute to several dapps' UAW totals?: The same wallet could contribute to separate dapp-level UAW figures through interactions with each application's tracked contracts. Those counts described participation in different applications. Adding them would not establish the number of distinct wallets across the combined group, because the same address could occur in more than one total.
Which general-ranking filters required PRO to work together?: The historical general-ranking interface reserved combined Balance, Users and Volume range filters for PRO members. Individual metric-range filtering was available more broadly. That distinction concerned simultaneous filter combinations, rather than a different definition of the underlying data. It describes the original interface, not a current membership offer.
Was an NFT collection's floor price its average sale price?: An NFT collection's floor price was its lowest listed asking price, while its average sale price summarized NFTs sold during a reporting period. These figures could move differently. Average price reflected completed sales, so it did not describe the value of every NFT in the collection.
Did Hot Contracts show dapps absent from the general rankings?: The historical Hot Contracts feature could surface active contracts from dapps not yet listed in the directory. Its unit of comparison was the smart contract, whereas a general-ranking entry represented a listed dapp. A trending contract therefore did not necessarily have a corresponding application-level ranking.
How did the activity sparkline differ from a rank history?: The activity sparkline plotted changes in the metric selected for the ranking, rather than changes in the position number. A UAW-sorted view showed wallet activity across its selected window. A Balance view showed changes in holdings, so an upward line did not by itself establish an improvement in relative rank.
What did the new-dapp filter select?: The new-dapp filter selected recently listed applications within the historical rankings. Under the developer plans described in May 2025, new Basic listings kept the 'new' badge for 7 days and new Premium listings for 14 days. The filter distinguished additions to the directory from the wider set of tracked dapps; it did not change the definitions of UAW, Volume or Balance.
Could the API return transaction counts for top-ranked dapps?: The original API's top-dapp data included transaction counts alongside UAW and volume. That provided an additional activity measure beyond the general table's documented sorting choices. These fields describe historical data access and do not establish that the original endpoints remain available after the platform's wind-down.
Does a high Volume figure mean a dapp earned high revenue?: A high Volume figure measures asset flows through tracked contracts and does not establish high revenue. Transferred assets can belong to the people interacting with an application. Establishing revenue requires distinguishing income the application earns from the total value passing through its contracts.