Destroyed supply
All tokens destroyed, including burns that fail the project's conditions. An unavailable number stays unavailable; it is never shown as zero.
zscal / PUBLIC LEDGER
Collections & burns
Open original ledger ↗Explore the original project's saved activity feed. Collection counts and qualifying burns come from its API; they have not been independently audited here.
SAVED SNAPSHOTProduced —
| Collection | Market cap | 24h volume | Holders | Qualifying burns | Amount in qualifying burns | Minimum burn | Details |
|---|---|---|---|---|---|---|---|
| Loading saved records… | |||||||
A symbol is not a unique identity. Use the full mint address to distinguish collections. Sorting by destroyed amount compares raw token counts, not economic value.
Accepted means the source API marked the burn as qualifying. It does not independently prove that a Zcash certificate was issued.
Saved Zcash registration data. A reported funding balance is not a guarantee of immediate issuance.
How registration and funding work
The original project describes an append-only Zcash register: anyone can add a collection, and entries cannot be removed. This is a project claim about its registration design.
The site says launch fees automatically fund each collection’s inscription address. A zero balance may indicate a pending top-up, but does not by itself prove one is pending. Check the confirmed balance before burning.
Anyone can add funding. Under the project’s rules, that address pays for its own collection’s inscriptions. This redesign does not accept deposits or operate the issuer.
Read the original funding explanation ↗MARKET
Price chart
The chart is provided by DexScreener and updates independently. The collection figures beside it are a saved snapshot. If the embedded chart is unavailable, open DexScreener directly.
READ THE RECORD CORRECTLY
Reading the ledger
Qualifying burns
Burn transactions the project's rules accept. The amount, token identity, memo, recipient and finality all matter.
Issued certificates
Zcash inscriptions linked to accepted burns. This is a separate issuance step, so a burn counter is not used as a certificate counter here.