What our data measures

Our Cardano mainnet node supplies blocks to a selective indexer. We match output payment script hashes against a reviewed registry sourced from each project’s official SDK or API. Each DApp page lists those hashes and its mapping source.

Observed contract transactions

We record successful transactions that create an output at a tracked payment script, or spend a tracked output that our indexer has already observed. A transaction is counted once for each DApp it touches, even if it creates or spends several matching outputs. A transaction touching two DApps counts once on each DApp page; the global distinct transaction count deduplicates it.

Reference inputs, unused script witnesses and failed transactions are excluded. Order placement, cancellation, liquidity actions and batched settlements can all produce activity. These counts are not trade counts or numbers of people.

Partial coverage and collection dates

Collection began on 1 November 2026. The exact start checkpoint and time appear alongside the data. Contracts, versions and actions outside the published registry are not covered. Spending an output created before our start checkpoint can be missed if it creates no tracked output. Counts therefore remain lower-bound observations, even after a full 24 hours has elapsed.

The directory shows a DApp after its first observation passes the three-block display delay. Projects with no recorded activity stay hidden until data arrives. The API registry and direct contract profiles can still include those projects; a hidden listing does not imply that a protocol is inactive.

The 24h figure is the count within the last 24 hours of available observations. Until 24 hours of data has been collected, it covers a shorter period. Zero means no matching event was observed in that period. Unknown financial metrics are shown as unavailable.

Freshness and confirmations

The feed is marked current when the indexer is running, it received a block within 180 seconds, and its checkpoint is no more than 10 blocks behind the node’s reported tip. This describes our ingestion pipeline; it is not an independent guarantee that the node has the latest network tip. We wait for three subsequent blocks before including transactions in DApp counters. This is a display delay, not finality. Rollbacks remove orphaned observations. Recent transaction evidence and the global raw count may include newer, provisional blocks.

Validation

We validate address checksums and mainnet payment credentials, retain matched transaction evidence, check duplicate handling and rollback recovery, and compare sampled transactions with an independent Cardano API. A mapping-source review confirms attribution, not a security audit or endorsement. Registry expansions are replayed into a new database from the original checkpoint; earlier database snapshots are retained.

View the dated validation report and sampled transaction IDs ↗

Financial data and swaps

This feed does not currently calculate TVL, trading volume, active wallets, yields or token prices. We do not infer them from transaction counts or contract balances. The swap widget obtains quotes separately from DexHunter. Future financial metrics require protocol-specific decoding and independently checked pricing data.