Dapp radar connects dapp discovery with blockchain activity data
Dapp radar organizes blockchain application data so you can discover decentralized applications and understand their recorded activity. These applications, usually called dapps, use smart contracts for some or all of their operations. Directory entries, activity metrics and market information answer different research questions. An active wallet count describes tracked addresses, while transaction counts describe recorded interactions. The platform’s ownership transition also separates its continuing brand from former token benefits and services.
- updatedOn this page
Bottom line: Wallet counts describe tracked addresses, so application coverage and reporting periods determine what a dapp activity figure actually measures.
Contract Coverage and Activity Records
Contract coverage determines which parts of an application’s blockchain activity contribute to its statistics. A smart contract is a program deployed on a blockchain. Applications can use several contracts, and a deployment on another network has its own records. A familiar application name therefore doesn’t establish that every feature or network contributes to the displayed total.
The underlying sequence starts with activity on a blockchain. An analytics system collects relevant records, associates them with an application and aggregates them into metrics. Its coverage determines what enters that calculation. Missing activity can reflect an untracked contract or unavailable data rather than an unused application. Keep the application, network and reporting period attached to any figure that you save.
Discovery, Portfolios and Data Access
Discovery starts with an application’s category and purpose. Dapp research spans decentralized finance (DeFi), exchanges, blockchain games, non-fungible tokens (NFTs) and social applications. Rankings help locate candidates, while individual activity records explain what those applications do on-chain. A position in a list doesn’t explain the transactions underneath it.
Different research tools answer different questions. An application view concerns a project’s activity; a portfolio view concerns a wallet’s holdings. NFT collection data concerns assets and sales, which needn’t match activity across an entire marketplace. Industry reports place measurements within a stated period. Those distinctions remain useful when several views display similar labels.
The earlier platform also offered an application programming interface (API) for retrieving dapp and NFT data programmatically. Its portfolio tools covered tokens, DeFi positions and NFTs. Those historical capabilities don’t establish that every former integration or account feature operates under the new ownership. A visible portfolio heading alone doesn’t demonstrate working position detection.
What Changed After the Platform Shutdown?
The original platform announced its shutdown in November 2025, and a May 13, 2026 update described a path forward for its brand and platform assets under new ownership. The ownership transition excluded the DAO and the RADAR token. The associated decentralized autonomous organization, or DAO, announced a formal wind-down without further maintenance, development or community services.
The public-facing brand and former token arrangements therefore have different histories. Older descriptions of membership, rewards and governance concern the former setup. They don’t establish continuing rights under the new owner. This distinction matters when a search result leads to an old feature announcement that still uses present-tense language.
What Does an Active Wallet Count Measure?
Unique Active Wallets (UAW) measures the number of distinct wallet addresses that interact with tracked dapp smart contracts during the reporting period. It doesn’t establish how many individual people used an application.
A person can control several addresses. Automated software can also generate transactions, so a larger wallet count doesn’t by itself prove human adoption.
Repeat activity from an already counted address increases its interactions without creating another unique address within that same period. Changing the period changes which addresses qualify. Daily counts therefore can’t simply be added together to obtain a distinct-wallet total for a longer period: the same address may appear on several days.
Games make the boundary especially visible. Some gameplay happens outside the blockchain, even when players own blockchain assets. A game can have active players who make no qualifying transaction during the measured period. Conversely, an asset transaction doesn’t prove that its sender played a game. Wallet activity and gameplay participation need separate descriptions.
Unusual transaction patterns can justify closer examination, but a chart alone doesn’t identify bots or prove manipulation.
Volume, Balances and Asset Values
Volume measures activity across an interval; a balance measures holdings at a point in time. The earlier dapp metrics defined volume through token transfers involving tracked contracts and balance through tokens held in those contracts. A trading-volume field has a narrower meaning when it counts trades. Neither measure automatically represents revenue. Currency-denominated values also move with asset prices, so a value increase doesn’t necessarily mean that more tokens entered an application.
Wallet Counts After a First or Repeat Interaction
Consider a hypothetical activity dataset with 38 unique active wallets and 118 qualifying transactions. The application scope, reporting window, wallet histories and counts are all illustrative inputs. Keep the window and tracked contracts fixed, with no records expiring or other activity arriving. You’re checking how one additional qualifying transaction changes the recorded totals.
First confirm that the transaction belongs to the tracked application and falls inside that window. If its wallet hasn’t appeared in the dataset, including the transaction produces 39 active wallets and 119 transactions. Record the updated totals alongside the scope. The wallet list then confirms that the added address was previously absent.
Starting again from the hypothetical 38 active wallets and 118 transactions, a repeat transaction from an address already present produces 38 active wallets and 119 transactions. In this case, inspect the existing address’s activity rather than treating the unchanged wallet count as a missing transaction. The record reconciles when the additional transaction appears under that address. If it remains absent, the counts alone don’t resolve the discrepancy; the contract coverage and transaction time need examination.
Does a Listing Establish a Dapp’s Safety?
A listing establishes discoverability, not a security guarantee for the application or its contracts. Activity metrics describe recorded behavior and can’t establish whether contract permissions expose assets to loss. A popular application can still have implementation defects or privileged controls. Sponsored visibility also answers a different question from measured usage. Keep any decision to authorize a transaction separate from the fact that an application appears in a directory.
Reconciling Analytics With Transaction Records
Transaction records and aggregated charts answer different questions. A chart describes a collection of activity; an individual record describes a particular blockchain operation. A transaction identifier, network and execution result help distinguish an actual operation from a pending request or an interface message. Where a transaction changes asset holdings, the resulting balances matter alongside its execution status.
A dashboard’s refresh cycle is separate from blockchain execution. A missing chart entry therefore doesn’t prove that a submitted action failed.
Reading activity data doesn’t require repeating the underlying transaction. Repeating an already completed action can create another operation and another fee. A browsing session can end without any blockchain action at all; using a dapp introduces that application’s own authorization and completion conditions.
For broad discovery, aggregated application data provides context that an isolated transaction lacks. For a specific missing operation, a block explorer provides the transaction-level detail that an aggregate chart cannot. Choose the view that answers the unresolved question.
What readers ask about Dapp radar
-
Can I Download Historical Dapp Activity Data?
- Historical data downloads were a feature of the earlier PRO membership. They included application activity data such as UAW, volume and transactions. That historical feature description doesn’t establish download availability under the new ownership. An accessible chart and an available export are separate capabilities, so don’t assume that viewing past activity includes access to its underlying dataset.
-
Do I Need to Authorize a Transaction to Read Public Dapp Statistics?
- Reading public dapp statistics doesn’t require authorizing a blockchain transaction. Viewing a directory or activity chart is a data request, not an instruction to move assets. An account requirement for a particular feature is a separate matter. A transaction or asset approval request introduces an additional action beyond reading the public figures.
-
How Should I Interpret an Empty Metric Field?
- An empty metric field doesn’t establish that the measured activity was zero. The value may be unavailable, unsupported for that application or absent from the displayed dataset. A numerical zero makes a different claim: the measurement returned no counted activity within its stated scope. Preserve missing values as missing when copying figures into a research note.
-
Is an Estimated NFT Value the Price That a Buyer Will Pay?
- An estimated NFT value isn’t an executable sale quote. The earlier analytics service used models to estimate individual NFT values, while completed sales recorded actual transactions. An estimate doesn’t create a buyer or a purchase commitment. A sale price depends on an accepted offer and the terms of the transaction, including which specific asset changes hands.
-
Does Closing a Portfolio View Erase Public Wallet Activity?
- Closing a portfolio view doesn’t erase transactions recorded on a public blockchain. The interface displays information that exists outside the browsing session. A public address can connect holdings and transaction history without revealing a person’s name, but sharing that address alongside identifying information can connect the two. Viewing privacy and blockchain record privacy are separate concerns.