Zcash network statistics

The Zcash network is at block 3,438,596, processing 4,963 transactions across 1,148 blocks in the last 24 hours, secured by 23.7 GSol/s of mining power, with 978 reachable nodes — as of 2026-08-06 16:52 UTC. Every metric below has its own section, its own source, and its own definition.

Zcash confirmed 4,963 transactions in the last 24 hours — an average of 4.3 per block over 1,148 blocks.

The count includes shielded transactions. Zcash publishes that a shielded transaction occurred and how many actions it contained, while its amounts, addresses and transaction graph stay encrypted — so daily transaction count is a usage measure, not a transparency measure. The one thing the chain does reveal about shielded activity is movement across pool boundaries: shielding, deshielding and turnstile migrations, all tracked on the shielded pools page. Over the same 24 hours 6,088 ZEC was shielded and 4,903 ZEC was deshielded.

Zcash targets a 75-second block interval, set at the Blossom upgrade in 2019 (before it, blocks targeted 2.5 minutes). Over the last 24 hours the network produced 1,148 blocks, an observed mean of 75.3 s per block. The chain tip is block 3,438,596.

The 75-second target is also the constant behind the halving countdown: blocks remaining × 75 seconds. Difficulty retargets every block, so the observed average tracks the target closely and the countdown self-corrects on every refresh.

The Zcash network hashrate is 23.7 GSol/s. Zcash mines Equihash (200,9), a memory-hard proof-of-work whose output is counted in solutions per second (Sol/s), not hashes per second — the two are not interchangeable units.

Hashrate is not directly observable; it is always inferred, either from difficulty or from observed block intervals. Both methods are estimates, which is why short-window hashrate charts are noisy and 24-hour averages are the honest unit.

Zcash's mining difficulty is 248,007,338. Unlike Bitcoin's fortnightly retarget, Zcash adjusts difficulty every block, from a moving average of recent solve times, so the network converges back on its 75-second target within minutes rather than weeks.

Difficulty is the network's own statement of what a block costs: it rises when mining power arrives and falls when it leaves. That is what makes it a usable hashrate proxy — difficulty × 8,192 ÷ 75 s is the implied solution rate.

ZecStats reports 978 reachable Zcash nodes — the count of distinct nodes that accepted an inbound peer-to-peer connection during the Blockchair crawler's most recent sweep. Separately, the indexer node whose RPC we read is holding 187 peer connections right now. Both numbers are published because they are not the same measurement.

So a node count is only meaningful with its method and its date attached. Ours: reachable listening nodes, Blockchair crawler, as of 2026-08-06 16:52 UTC. When a figure elsewhere disagrees, check what it counts before concluding either is wrong.

The Zcash mempool holds 13 unconfirmed transactions. With a 75-second block target, pending transactions normally clear within a block or two, so the count is usually small — what is worth watching is a mempool that stays large across many blocks, which is what a real backlog looks like.

The chain occupies 257.2 GB on disk on the node ZecStats reads, which reports itself as /Zebra:6.2.3/. Chain size varies with implementation and index settings, so read it as one current node's state rather than a universal figure.

zcashd, the original Zcash node implementation, reached end of support at block 3,417,100 on July 18, 2026. Ten days later, at block 3,428,143, NU6.3 "Ironwood" activated — sealing the Orchard pool and opening a fifth shielded pool. Two protocol-level changes ten days apart, which is why the node software string above matters more than usual right now; the migration itself is tracked on the Ironwood page and the sealed pool on the Orchard pool page.

A figure ZecStats cannot source is left blank rather than estimated, and a degraded source is stamped stale with a visible warning instead of quietly serving an old number. The full per-metric provenance is on the methodology page.

Same dataset, other questions: Zcash shielded pools · what percentage of ZEC is shielded · Ironwood migration tracker · Ironwood reconciliation · Orchard pool balance · how many Zcash there are · halving countdown · ZEC price · methodology · data downloads · raw JSON at /api/zec/summary.