Indexed ZcashBlockchain Data

Zcash launched on 28 October 2016 as the first production chain to ship zero-knowledge shielded payments. It descends from Bitcoin’s codebase, so the transparent side is a UTXO ledger with the same 21 million cap, mined with Equihash proof of work. Two things diverge. Blocks target 75 seconds rather than ten minutes, halved from 150 by the Blossom upgrade of December 2019, and the subsidy has halved every 840,000 blocks since Canopy in November 2020. The larger difference is the second ledger. Alongside transparent outputs, ZEC can sit in a shielded pool where amounts and parties are encrypted and the chain publishes only note commitments, nullifiers and proofs. Three pool generations have shipped: Sprout at launch, Sapling in October 2018, and Orchard with the network upgrade of May 2022, which also introduced unified addresses that bundle several receiver types into one string.

SonarX indexes blocks and headers, transparent transactions with their inputs, outputs and locking scripts, the derived output set and the positions built from it, and the shielded components each transaction carries, including the value it moves across a pool boundary. The same normalized model covers every network SonarX indexes, so the transparent side of this chain answers the same questions as any other UTXO ledger.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Kafka streaming can be enabled for Zcash on request.

The interesting work is at the boundary. The transparent ledger is a UTXO walk, so positions are derived from creations and spends in the ordinary way. Inside a pool there is nothing to attribute: commitments and nullifiers prove that a note existed and was spent without saying by whom or for how much. What the protocol cannot hide is net flow, since a shield or a deshield changes transparent value and has to balance, so the indexed history carries value in and value out per pool generation. Coverage therefore marks where a trail stops instead of guessing a path through it, and the three note formats are kept apart rather than summed.

Monetary research is the first workload and the one this chain is unusual for: how much ZEC sits transparently versus in each pool, and how that split moves after a protocol change, is a question almost no other network poses. Exchange and custody reconciliation is the second, and it is harder than on a plain UTXO chain, because a deposit can arrive from a shielded address with no sender to record, so internal attribution has to carry the weight. Compliance work is the third, and its value lies in stating precisely what the chain does and does not publish rather than inferring links that were never recorded. Miner and issuance accounting is a fourth, spanning a block target that changed and a halving schedule that was reset. Wallet analytics covers the address-level side across chains, and Dash is the usual comparison when the question is about optional confidentiality.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Zcash history is available now, and streaming is provisioned on request. Say whether shielded pool flow is in scope, since that determines how much of the chain a position can account for. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.