Dappradar
Dappradar rankings and the activity behind UAW counts
Dappradar rankings compared decentralized applications through tracked smart-contract activity, using unique active wallets (UAW) to measure distinct participating wallet addresses. The count described activity within a selected period, rather than the number of people using an application. Category, blockchain coverage, and the chosen metric shaped each ranking. The original platform announced its wind-down in November 2025, so these mechanisms describe its historical service. Saved rankings retain meaning within the reporting scope that produced them.
Bottom line: Historical UAW comparisons require matching reporting periods and tracking scope, because contract coverage changes what the counts represent.
Comparing activity within a selected ranking view
With category, blockchain, and reporting period fixed, descending UAW order showed which tracked applications attracted the greatest number of distinct active wallet addresses. Filters defined the comparison group. Sorting by volume or balance answered a different question within that group. Rankings 2.0, introduced in July 2023, added subcategories, growth sorting, and data-range filters. Category-specific views exposed relevant metrics for games and decentralized finance (DeFi). A position belonged to a particular view; it did not describe every application across every network.
The contract activity behind a UAW entry
Dappradar built application statistics from the contracts linked to a product listing. Standard UAW tracking counted distinct wallet addresses that transacted with those tracked contracts.
Contract coverage
Developers supplied contract addresses for tracking. A product page could group deployments across several blockchain ecosystems, while chain filters narrowed the displayed data. An incomplete contract list could omit qualifying activity. A changed list could change the coverage behind a later count, even when the product name stayed constant. Historical comparisons therefore needed attention to the contracts and networks represented by each observation.
UAW counted an address once within the selected dapp and reporting period. Repeated qualifying transactions increased transaction activity without repeatedly adding that address to the same UAW count.
Account abstraction decoding
ERC-4337 account abstraction introduced another tracking dependency. Bundlers combined multiple wallet operations into a single blockchain transaction. Dappradar documented an integration that decoded this activity using the EntryPoint contract and relevant function definitions. Its configuration distinguished EntryPoint functions from smart contract wallet functions. Tracking completeness therefore depended on decoding support alongside the application contract list. The outer transaction alone did not describe each participating wallet when a bundler submitted multiple operations.
That configuration applied to future transactions after integration. Historical recalculation required a separate support request, so enabling the parser did not automatically make earlier observations comparable.
UAW alongside transaction, flow, and balance measures
UAW, transactions, and volume described different aspects of tracked activity: participation breadth, recorded actions, and the value of token flows. New UAW was a follow-up measure on dapp pages, with its own coverage limits.
| Measure | Recorded property | Useful interpretation | Measurement limit |
|---|---|---|---|
| UAW | Distinct active wallet addresses | Breadth of tracked participation | Addresses did not identify unique people |
| Transactions | Tracked on-chain transactions | Frequency of recorded actions | Chain and decoding rules defined coverage |
| Volume | Dollar value of tracked token flows | Scale of asset movements | Flow did not establish protocol revenue |
| Balance | Value of tokens in tracked contracts | Assets held at a measurement point | A snapshot, not cumulative period flow |
| New UAW | Newly observed active wallets | First recorded dapp participation | Two-year lookback; chain coverage could differ |
Volume covered token flows within the stated period. The general definition included transfers into and out of tracked contracts. The Internet Computer integration specified incoming transaction value for canisters, its smart contract units. A volume figure did not establish protocol fees, revenue, or user profit. Direction and valuation rules remained part of its meaning.
Balance represented the value of tokens held in an application’s tracked smart contracts. It described holdings at a measurement point. Summing successive balance observations would repeatedly count retained assets. Neither a high balance nor heavy wallet activity established an audit or security certification.
How did the time window affect UAW rankings?
The reporting window set which wallet interactions qualified for the count, so a brief burst could influence a daily view differently from a longer activity window. General rankings offered 24-hour, seven-day, and thirty-day periods. Wallets active outside the chosen window did not contribute to that observation. Longer periods captured activity across more time; they did not establish continuous use throughout it. Comparisons needed matching periods and metric definitions, especially when an industry report described average daily UAW instead of distinct wallets across an entire period.
New UAW and activity patterns beyond wallet counts
New UAW distinguished newly observed wallet participation, while transaction patterns and off-chain activity explained limits that a UAW total alone could not resolve.
First-time recorded participation
Dappradar introduced New UAW in September 2025 to describe wallets with newly recorded dapp interactions. The metric used a two-year lookback to check for earlier interactions with that application. New UAW formed a subset of total UAW within matching coverage and timeframes. It identified newly observed addresses within that history, rather than proving that their owners had never used the product. Supported networks varied, and a multichain dapp could have incomplete New UAW coverage.
Automation and off-chain use
Automated wallets could contribute on-chain transactions. A stable relationship between UAW and transaction totals could prompt examination of automation, although the relationship did not establish a bot count. Automated activity also had legitimate uses in decentralized finance. At the other boundary, gameplay or social activity that stayed off-chain fell outside standard contract tracking. A product that put more actions on-chain could generate a different activity pattern from one that used blockchain transactions only for asset transfers or rewards.
Historical rankings and category-specific comparisons
An old position supplies no current activity measurement.
Application-level records gave rankings further context through transaction history and contract coverage. The API supported retrieval of UAW, transactions, and volume for further analysis, while the Portfolio described assets associated with individual wallets. Capital analysis used total value locked (TVL) and adjusted TVL (aTVL). The latter valued tokens at their prices from the start of the measurement period. UAW addressed the breadth of tracked wallet participation; evaluating capital held in DeFi contracts required valuation measures. NFT trading rankings addressed another task through collection sales, trading volume, and traders.
Frequently asked questions about Dappradar rankings
Can one wallet appear in the UAW counts of several dapps?
One wallet could contribute to each dapp’s UAW count when it made qualifying transactions with each application’s tracked contracts. Distinctness applied within the relevant application and period, so adding application totals could count the same address repeatedly. Such a sum did not describe distinct wallets across the wider ecosystem.
Should daily UAW figures be added to reconstruct a weekly count?
Adding daily UAW figures can count a returning address on several days. A distinct weekly count requires the combined set of qualifying addresses, with duplicates removed across the entire window. An average of daily counts answers another question. Keep these aggregations separate when comparing saved rankings with historical industry reports.
Why could a large percentage increase accompany a small UAW count?
A percentage increase measures change relative to a positive starting count, so a small starting base can produce a large percentage movement. Growth sorting described relative change, while sorting by UAW described the size of tracked wallet participation. The percentage alone did not establish a large audience or durable activity.
Did an advertisement at the top of a ranking indicate first place?
An advertising placement did not establish first place by the selected activity metric. Historical rankings included rotating promotional rows with an Ad label. Their position reflected advertising placement, while the ordinary ranked entries followed the selected sorting criterion. The label mattered when interpreting a saved screenshot of the table.
Could a simple wallet-to-wallet transfer raise a dapp’s UAW?
A simple transfer between wallets did not qualify merely because it appeared on a blockchain. Standard UAW tracking required the relevant interaction with a dapp’s tracked smart contracts. Sending assets to another wallet therefore did not automatically add either address to that application’s UAW count.
How did the Activity line relate to the selected column?
The historical Activity line showed the trend of the metric selected for the ranking over its reporting window. A UAW view displayed wallet-activity movement, while a balance view displayed changes in holdings. The small chart supplied time context that a single table value could not show.
Were collectibles rankings equivalent to NFT trading rankings?
Collectibles rankings measured activity involving a collectible project’s tracked dapp contracts, while NFT trading rankings described market activity such as sales, traders, and trading volume. Those measurements could cover different interactions. A high UAW position for a collectible project did not automatically establish a leading position in NFT sales.
Does a missing UAW value mean an application had no users?
A missing UAW value does not establish that an application had no users. A blank field supplies no count, while a recorded zero refers to reported activity within its tracking scope. Neither value describes off-chain visits or gameplay.