On-chain data and coverage

On-chain information is network-specific evidence. Read the network, address, source, coverage label, and time window together before drawing a conclusion.

What a deployment shows

Each deployment listed on a project is shown as its own entry, with its own network, address, and provenance.

Field	How to interpret it
Network and environment	The exact chain, and whether the address is on mainnet or a test network
Role	What the deployment is for: core protocol, router, factory, bridge, governance, treasury, oracle, token, registry, or other
Address or resource identifier	The chain-native identifier for that deployment, copyable and linked to a block explorer
Contract details	Source verification, license, compiler, deployer, and whether the contract is an upgradeable proxy
Activity figures	Interactions, participants, repeat participant share, and success rate for the selected window
As of	When the displayed snapshot was captured
Source	The provider the snapshot came from
Coverage range	The period Dapping has continuously collected for that deployment

Metric names follow the network. An EVM deployment counts calls and callers; a Solana program counts program invocations and fee payers; a Midnight contract counts public contract transactions and publishes no participant figures at all.

Activity windows

Activity is reported over a selectable window of 7, 30, or 90 days. Figures from different windows are not comparable, and neither are figures from different networks.

Coverage labels

Every activity figure carries one of four labels.

Label	Meaning
Complete	The provider returned full history for the selected window
Lower bound	Activity exceeded the provider’s bounded history, so the value is an observed minimum and is shown with a trailing `+`
Partial	Some deployments, or part of the selected history, do not have complete activity coverage
Unavailable	Activity analytics are not available for these deployments

An unknown value appears as Unavailable, never as zero.

Status markers on a deployment

Marker	Meaning
Verification pending	The deployment has been recorded but not yet confirmed against the network
Network confirmation required	The stated network does not match what was found, and must be confirmed
Temporarily unavailable	The source could not be reached or returned nothing usable for this address
Stale snapshot	The most recent successful snapshot is older than the expected refresh point
Upgradeable proxy	The contract can be pointed at different implementation code

Fees, success, and what they are not

Fee totals are actual network transaction fees in each network’s native currency. They are not protocol revenue. Success rate is the share of measured interactions that completed without a provider-reported execution failure. It is not a measure of whether the outcome was the one a user wanted.

On-chain metadata is not a security audit, proof of legal ownership, investment recommendation, revenue measurement, or guarantee that a contract, token, or destination is safe.

Evaluate a project and understand its on-chain information

Apply these terms while evaluating a specific project.

Supported networks

Check which networks carry activity, metadata only, or an explorer link.

​What a deployment shows

​Activity windows

​Coverage labels

​Status markers on a deployment

​Fees, success, and what they are not

​Related guides

Evaluate a project and understand its on-chain information

Supported networks

What a deployment shows

Activity windows

Coverage labels

Status markers on a deployment

Fees, success, and what they are not

Related guides