Dappradar combined dapp discovery with analytics of tracked blockchain activity
Dappradar's original platform offered discovery and analytics for decentralized applications (dapps), with usage metrics focused on tracked smart contract activity. Its listings, rankings and project pages helped explain what apps offered and how their blockchain activity compared. Standard wallet counts excluded off-chain sessions, so they could understate activity in apps using centralized servers. The original team announced a wind-down in November 2025; a May 2026 update reported new ownership of the brand. Its historical data remains useful when the observation period and measurement scope match the research question.
Updated
Listings and project pages connected discovery with data
The platform combined a searchable app directory with project-level analytics, giving descriptions and measured activity separate roles within the same research environment.
Descriptions explained the application
Project pages carried descriptions, screenshots and other information developers supplied about their applications. Categories and blockchain filters helped narrow discovery to relevant products. The Developer Dashboard let teams submit projects and manage existing listings. This descriptive layer explained intended functionality; its claims needed different interpretation from observed contract activity. Developers could also identify the smart contracts belonging to their products, linking the listing to the blockchain components the platform monitored. A product spanning several networks could have a combined page with separate blockchain views.
Contract coverage defined the statistics
Project pages supplied the underlying activity data used in rankings. Their contract lists mattered because a metric described the contracts the platform tracked. Missing relevant contracts could leave part of a product's activity outside its reported figures. A complete product description therefore did not establish complete statistical coverage. Changes to those monitored contracts also affected the meaning of historical comparisons, even when the app retained its name.
How much app usage did active wallets represent?
Unique active wallets (UAW) represented addresses interacting with tracked smart contracts during a selected period, which covered only the blockchain-visible portion of app usage.
Wallet addresses and people
One person could contribute multiple addresses to a dapp's unique active wallet count. Automated activity could also contribute to recorded interactions. The metric therefore described wallet participation without establishing a count of individual people. Repeated activity from one address also differed from participation by additional addresses. Comparing the same observation period helped keep those meanings consistent.
Sessions outside the blockchain
Games and social applications could run sessions on centralized servers while using smart contracts for asset-related actions. Those sessions did not enter standard on-chain activity counts unless they produced tracked interactions. A smaller wallet count could therefore coexist with substantial activity inside the application. Custom integrations could address additional activity; ordinary contract metrics alone could not describe the entire experience.
New wallet participation
In September 2025, New UAW added a view of wallets interacting with a dapp for the first time within its historical check. It examined two years of prior interactions. That lookback qualified the meaning of new participation, and coverage could differ between networks within a multichain product. A wallet newly interacting with an app was not necessarily a newly created wallet.
Transaction volume and contract balances answered different questions
Transaction volume measured value moving through tracked contracts over a period, while balance measured the value of assets held in those contracts. A flow and a holding described different aspects of activity. Repeated movement could contribute to substantial volume without leaving a comparable balance behind. Transaction count measured the number of transactions to and from tracked contracts rather than their monetary value. None of these quantities directly established profit, revenue or the number of human customers. Their relationship depended on what the application actually did with its contracts.
The dollar value of a balance could change when token prices moved. Decentralized finance (DeFi) views also included total value locked, or TVL, and adjusted TVL. Adjusted TVL held token prices fixed at the start of the selected measurement period. This helped distinguish changes in deposited quantities from changes in valuation. It did not turn locked capital into a measure of protection against loss.
Gaming, DeFi and NFT research required different context
Category-specific research needed metrics matching the activity under discussion, because playing a game, depositing capital and trading a collectible produced different economic signals. Gaming analysis especially needed to distinguish play sessions from asset-market activity. A game could use smart contracts for trading items while handling ordinary gameplay elsewhere. Its transaction statistics then described one component of the product's use.
DeFi capital and activity
Decentralized finance research used locked capital and transaction activity to describe participation in financial applications. Wallet counts added context about interacting addresses. A larger balance did not explain whether the underlying contracts were secure or whether positions carried borrowing exposure. Likewise, high activity did not identify how much value an application retained. Those questions required information about the particular product and its mechanisms beyond the activity totals.
NFT collections and marketplaces
Analytics for non-fungible tokens (NFTs) separated collection activity, individual sales and marketplace activity. Trading volume, sales counts and participating traders each described a different part of the market. A collection floor price described its lowest listed asking price, while completed sales recorded actual transactions. Those measures separated offers awaiting a buyer from trades participants actually completed.
Portfolio views and Hot Contracts changed the unit of analysis
The portfolio focused on assets associated with a wallet, while Hot Contracts focused on activity around individual contracts, including contracts outside established app listings. Earlier portfolio views brought together token holdings, DeFi positions and NFT collections on Ethereum, BNB Chain and Polygon. They also supplied estimated NFT values. Coverage depended on the feature and blockchain involved; support elsewhere in the platform did not establish portfolio coverage.
Hot Contracts widened discovery to active contracts before a project necessarily had a directory listing. Its UAW metric counted distinct wallets making direct transactions, including successful transactions, failed transactions and approvals. That definition mattered when interpreting its figures alongside general dapp statistics. Descriptions generated with artificial intelligence summarized verified contracts with available source code, without establishing a security audit.
API access and PRO extended the analysis
The application programming interface (API) exposed structured analytics for software integrations, while PRO features expanded access to historical data, exports and selected filters within the platform. API data included dapp activity, NFT sales and collection metrics, alongside token information. External products could incorporate these datasets into their own interfaces or models.
PRO users could export historical dapp and NFT data as comma-separated values (CSV) files for analysis outside the browser. Both access methods preserved the underlying dataset's boundaries. Exporting wallet activity did not add missing off-chain sessions, and programmatic delivery did not establish human identities behind addresses. Package limits and membership terms belonged to their applicable service period; historical offers did not establish current access or pricing.
RADAR and community features supported participation
RADAR supported participation in the decentralized autonomous organization (DAO) and token-linked PRO access, connecting parts of the platform's community model with its premium research features. Token holders had voting rights, and the governance process supported proposals concerning the platform's development.
Boosting Power gave participants a way to promote projects and increase their visibility. This promotional mechanism served a different purpose from rankings based on measured contract activity. Visibility gained through boosting did not demonstrate organic usage or a security assessment.
Quests and airdrop campaigns also formed part of discovery and community participation. Their requirements belonged to individual campaigns. The portfolio included access to Token Swap, and earlier NFT tools supported fixed-price listings of owned NFTs through the OpenSea integration and transfers to other wallets. These features linked discovery with interaction, although their availability and conditions depended on the relevant integration. A historical description of those functions does not establish an active transaction service today.
What happened to the original Dappradar platform?
The original team announced its decision to wind down the platform on November 17, 2025. The plan included ending blockchain and dapp tracking and shutting down associated services. Historical charts and exported records describe their own observation periods. They cannot establish fresh activity after tracking ends. In its May 13, 2026 update, the DAO announced new ownership of the brand and platform assets, excluding the DAO and RADAR token. Current research needs a functioning data provider with identifiable coverage and update behavior.
Which research views suited different questions?
App-level rankings suited comparisons between products, portfolio views organized wallet holdings and Hot Contracts showed activity around individual contracts. Those differences determined which question each view could answer.
| Historical research option | What its data could establish |
|---|---|
| General dapp rankings | Relative tracked wallet activity or value movement; off-chain sessions remained outside standard counts. |
| DeFi rankings | Tracked locked capital and price-adjusted comparisons, without establishing protection of deposits. |
| NFT rankings | Collection, sale and marketplace activity, without guaranteeing a future buyer or resale price. |
| Portfolio | Covered wallet holdings and estimated values, without guaranteeing proceeds from selling assets. |
| Hot Contracts | Individual contract activity under its own counting rules, without certifying contract security. |
| API | Structured access to the covered datasets, with the same measurement boundaries as their underlying data. |
Replacement tools also divide along these lines. Block explorers expose contract records; portfolio trackers organize address-level holdings. Specialized market analytics focus on financial or collectible activity. Application analytics cover sessions outside the blockchain when the operator collects them. These approaches answer different parts of the research question. Comparisons remain meaningful only while their periods, coverage and metric definitions align.
Common questions
Did browsing dapp listings require buying RADAR?
Basic dapp discovery did not require buying RADAR. Public rankings and project information provided a starting point for research, while token-linked PRO membership unlocked selected additional features. Buying or staking tokens belonged to particular premium arrangements, rather than being a general requirement for reading listings. Those historical access arrangements do not establish what a service offers today.
Could a project appear before its application launched?
Projects could appear as upcoming dapps before launch. The submission process distinguished released applications from planned releases and other Web3 projects. A released dapp needed smart contract information, while an upcoming submission could describe its intended launch. An upcoming listing therefore conveyed project information without establishing an operational application or existing on-chain usage.
Was tracking another wallet the same as controlling its assets?
Viewing another wallet's public holdings gave no control over its assets. The portfolio supported watchlists for addresses users did not own. A watchlist entry organized the available holdings data; it did not transfer ownership or grant permission to move tokens. The address alone also did not establish who controlled the wallet or why its owner held particular assets.
How reliable were estimated NFT portfolio values?
NFT portfolio values were estimates rather than committed purchase offers. The valuation used floor prices, past sale prices and machine learning to estimate holdings. An individual asset could differ from a collection's cheapest listing, and a past sale did not promise another buyer at that price. The estimate described a valuation model; actual sale proceeds depended on an executed transaction.
Is a historical listing evidence of a smart contract security audit?
A historical listing alone does not establish a smart contract security audit. The directory submission process collected project information and contract addresses for review and inclusion. An audit examines a specific codebase and has its own scope and findings. Directory approval, contract tracking and promotional visibility therefore cannot substitute for evidence of that separate assessment.
Which protections did portfolio spam filtering provide?
Portfolio filtering helped reduce the visibility of spam tokens and NFT collections. The platform used machine learning and community reports to improve that filtering. These controls concerned what appeared in the holdings view; they did not establish the legitimacy or transferability of every displayed asset. A portfolio value for an unfamiliar token did not itself demonstrate an available buyer.
Did the shutdown announcement settle the future of RADAR and its DAO?
The November 2025 shutdown announcement left RADAR and DAO matters for separate communications. It addressed closing the analytics platform and its associated services, while treating community governance and the token separately. The November announcement alone did not establish a redemption arrangement. A May 13, 2026 update later announced the DAO's formal wind-down, with no further maintenance, development or community services. It excluded the DAO and RADAR from the platform's ownership transfer and stated that the new owners had no obligations toward either.