Dapp radar
Dapp radar rankings need matching timeframes and coverage for meaningful comparisons
Dapp radar rankings support meaningful comparisons when the records share a measurement period, blockchain coverage and sorting metric. Begin with those settings before comparing positions or interpreting changes in unique active wallets and volume. A longer observation window captures a different slice of activity, while a narrower category changes the competing applications. Saved figures also retain the definitions and coverage that applied when someone recorded them. Compare wallet counts with wallet counts, distinguish transaction value from balances and keep each record’s date attached. These choices determine whether a difference describes activity, a changed comparison group or incompatible measurements.
- updatedBottom line: Matching measurement periods, blockchain coverage and metric definitions makes saved activity figures comparable, while rank alone leaves those differences hidden.
Wallet, Volume and Filtered Ranking Views
A wallet-sorted list and a volume-sorted list answer different questions about the same applications. The former orders recorded wallet participation; the latter orders measured asset flows. Neither establishes a universal winner.
The earlier rankings allowed filtering by blockchain ecosystem. Category filters also narrowed the comparison group, while sorting changed the order within it. These options remain useful distinctions when interpreting saved tables.
| View Option | Comparison Basis | What Must Match | Interpretation Limit |
|---|---|---|---|
| UAW sorting | Distinct interacting wallets | Period and tracked coverage | Wallets don’t equal people |
| Volume sorting | Measured transaction value | Period, currency and transaction scope | Value moved doesn’t establish revenue |
| Balance sorting | Value held in tracked contracts | Snapshot time and asset coverage | A balance isn’t period activity |
| Single-chain filter | Applications within the selected ecosystem | Chain selection, period and metric | Other deployments fall outside that selection |
| Category filter | Applications within a selected category | Category selection, chain scope, period and metric | Position applies to that comparison group |
| All-category view | Tracked applications across categories | Chain scope, period and metric | Different application functions affect interpretation |
| Keep the comparison group fixed when comparing positions, and keep metric definitions fixed when comparing values. | |||
The Relationship Between Wallets, Transactions and Value
The same tracked activity can contribute to several metrics without making those metrics interchangeable. Unique active wallets count distinct wallets interacting with a dapp’s tracked smart contracts during a measurement period. Repeated interactions can increase transaction counts without adding another distinct wallet.
Participation and Interaction Frequency
Wallet counts describe the breadth of recorded wallet participation. Transactions describe how often recorded interactions occurred. An application with frequent interactions per wallet can therefore look different under these measures. Comparing their relationship requires identical periods and coverage.
Movement and Holdings
Value Moving Through Contracts
Volume measures transaction value within the tracked scope. Its meaning depends on the operations included, so general transaction volume and a specifically defined trading-volume series need separate treatment.
Value Remaining in Contracts
Balance describes holdings at a particular time. Adding balances across successive dates repeatedly counts assets that remain in place. A balance comparison can describe changes in holdings’ value, whereas a volume comparison describes measured flows.
Which Timeframe Makes Two Dapps Comparable?
A shared interval makes activity totals comparable when both records also use the same coverage and definitions. Match the duration and its endpoint, rather than relying on a familiar period label.
A rolling window ending at different times contains different activity. A calendar period also differs from an equally long rolling interval when their boundaries don’t match. Retain start and end times where available, together with the timezone. For historical comparisons, distinguish a complete interval from one that was still accumulating activity.
Longer periods answer questions about activity across a broader interval. For windows with the same endpoint, shorter periods concentrate on more recent activity. Neither duration automatically produces a better comparison; the useful choice follows the question, and both applications need the same choice.
Chain Coverage Beneath the Application Name
Matching application names doesn’t establish matching blockchain coverage, particularly when an application has deployments across several networks.
A chain-specific record describes the tracked deployment within that ecosystem. A combined record may include additional deployments. Comparing those totals without preserving their scope can make broader coverage look like stronger activity.
Contract coverage matters within a chain too. Applications can use multiple contracts, and analytics only describe the contracts or integrations included in their measurement. A change in tracked coverage can therefore change the recorded total without an equivalent change in underlying participation.
Retain coverage details beside each saved figure when they’re available. If a record doesn’t identify its included deployments, describe its scope as unspecified. The application name alone can’t supply the missing boundary. This matters particularly when reconciling a ranking row with a more detailed activity record.
Category Boundaries and Comparable Actions
A category creates a comparison group, while each application’s mechanics determine what its recorded activity means. Two applications can share a category yet require different numbers of blockchain interactions for similar amounts of use.
Some applications place much of their activity on-chain. Others use the blockchain for only part of the experience. Lower recorded interaction counts can consequently reflect different product mechanics. A comparison of blockchain activity doesn’t automatically compare total engagement across those products.
Category-specific positions also use a different comparison group from positions across all categories. Keep those labels attached when quoting a rank. The narrower position answers where an application sits among its category peers, rather than across the entire tracked list.
Can Daily Wallet Counts Be Added Into a Weekly Total?
Daily unique wallet counts can’t simply be added to obtain distinct wallets across the combined week. A returning wallet can appear in several daily counts, so their sum counts some participants repeatedly.
A weekly distinct-wallet calculation needs the union of the daily wallet sets: each wallet counts once across the full interval. Daily totals alone don’t reveal which wallets overlap. They therefore can’t reconstruct that union exactly.
Daily volume totals have a different aggregation rule. They can form a longer-period total when their intervals don’t overlap and their transaction scope, currency and valuation treatment remain consistent. Missing intervals break that calculation. Overlapping rolling windows also count some of the same activity more than once.
Does a Higher Rank Mean Activity Increased?
A higher rank can occur without increased activity because position depends on the other applications in the list.
Competing applications may decline, disappear from the comparison group or move under a changed filter. An application’s own metric may even fall while its relative position improves. Absolute values and positions therefore describe different changes.
Percentage changes introduce another comparison. Their meaning depends on the starting value and the reference period. A change calculated against a smaller baseline can look larger without representing a larger absolute increase. Keep the underlying values available when interpreting percentages, and don’t infer the reference interval from the rank column.
Historical Records and Changing Definitions
Saved rankings describe the measurements captured at their recorded times, including the definitions that those versions used.
A familiar heading doesn’t prove continuity between an older record and a later interface. Columns, category assignments and tracking coverage can change. Treat records from different versions as comparable only to the extent that their measurement rules match.
The data’s endpoint can also differ from the moment someone saved a screenshot. A capture time establishes when the record was preserved; it doesn’t establish when every underlying metric last updated. Keep both times when the record provides them.
Preserving an original record alongside working notes keeps later interpretations reversible. Reordering copied rows doesn’t change the historical values, but overwriting their labels can remove the context needed to interpret them. A record without its period or metric definition supports a narrower conclusion than a fully labelled comparison.
Daily Averages, Period Uniques and Activity Quality
Similar wallet terminology can describe different calculations, so read the aggregation label before comparing the displayed values.
Daily Average UAW
A daily average describes the average daily count across an interval. It answers how many distinct wallets participated on an average day within that measurement. It doesn’t identify every distinct wallet that participated during the whole interval.
Distinct Wallets Across the Period
A period-wide unique count removes repeat appearances within that full period. Comparing it directly with a daily average mixes aggregation methods. Neither statistic alone reveals whether the same wallets consistently returned.
Automated systems can control wallets that contribute to dapp activity metrics. Transaction frequency can help describe their behavior, but a high or low aggregate ratio doesn’t establish who controlled the wallets. Ranking data therefore can’t independently turn wallet participation into a count of individual people.
The Limit of a Matched Ranking Comparison
Matched records show whether an application recorded a higher, lower or equal value for a specified metric within the selected scope and interval, at the available precision. That conclusion doesn’t establish a lower cost of use. Transaction costs follow the operations, network conditions and application charges involved. Nor does a position describe wallet permissions or the value of assets in a personal portfolio. Those questions require their own inputs; the ranking remains an activity comparison.
Frequently asked questions about Dapp radar rankings
Can I Treat an Application Missing From a Saved Ranking as Inactive?
An absent row doesn’t establish inactivity. A saved list may contain only part of the results, apply filters or omit an application that wasn’t tracked within that scope. Describe the application as absent from that record unless the record separately establishes zero activity for the complete interval.
How Should I Compare Dapps With Identical Rounded Wallet Counts?
Identical rounded counts don’t establish an exact tie. Abbreviated figures can conceal differences that affect the displayed order. Use the underlying precision when the record includes it. Otherwise, preserve the displayed position and describe the values as equal at the available precision, without inventing a tie-breaking rule.
Which Baseline Should I Use When an Earlier Activity Value Is Zero?
A percentage increase from a zero baseline is undefined under the usual percentage-change calculation. Report the absolute change and identify the zero starting value instead. Replacing that baseline with an arbitrary positive number would manufacture a percentage that the saved records don’t support.
Is the Sum of Several Dapps’ UAW Counts Their Combined Audience?
Adding several dapps’ UAW counts can count the same wallet more than once. A wallet may interact with multiple applications during the selected period. A combined distinct-wallet count requires deduplication across those applications, and even that result counts wallets rather than individual people.
When Should an Incomplete Month Be Excluded From a Volume Comparison?
An incomplete month should remain separate from complete-month totals when the question concerns total monthly activity. A comparison through the same elapsed portion of each month can answer a narrower question. Label that partial interval explicitly rather than presenting its total as a finished month.
Could Spreadsheet Formatting Reverse the Order of Saved Ranking Values?
Spreadsheet sorting can produce an incorrect numeric order when imported values remain text. Currency symbols, abbreviations and separators can affect interpretation. Preserve the original column, convert only values whose units are clear and sort the numeric working column. Missing values should remain distinct from measured zeros.
Will Transaction Volume Show the Fees That a Dapp Earned?
Transaction volume doesn’t directly measure the fees that an application earned, because a fee calculation also needs the chargeable operations, applicable fee rules and any relevant exemptions or allocation terms, none of which follows from the application’s position in a volume ranking.