The Zcash network has been producing no new blocks for more than four hours — far past the usual 2.5-minute target — leaving thousands of transactions stuck in the mempool with zero confirmations. Around 96 blocks were missed during the halt, and deposit services on major exchanges like Binance and Kraken have effectively frozen as a result. ZEC's price slipped 2% in the hour after the four-hour mark was hit, though the bigger question is what caused the stoppage.
What went wrong?
No one has confirmed the root cause yet. Community developers from the Zcash Foundation and Electric Coin Co. forums have floated two main theories: a consensus bug triggered by a recent minor node update, or an unforeseen interaction with the network's difficulty adjustment algorithm. A 51% attack has been largely ruled out — the halt shows a total cessation of block production, not a chain reorganization. Whether both Zcashd and Zebra clients are affected, or only one, remains unconfirmed.
Market and exchange fallout
With no block confirmations, Binance and Kraken have effectively paused ZEC deposits. That leaves traders unable to move coins onto or off of those platforms. The price drop was modest — 2% — but the structural outlook is bearish until block production resumes and an official explanation confirms the halt is contained. ZEC had recovered from under $1 in July 2024 to around $250 by April 2026, with a 16% spike to $372 on April 9 and a 30% move in May that put the coin above $600. This halt could test that rally.
Not the first network stress
Zcash's dual-client architecture — Zcashd and Zebra — has caused consensus stress before. In early June 2026, an emergency Zebra consensus patch was required. Separately, an Emergency Orchard Upgrade temporarily paused shielded transactions. This pattern suggests the network's complexity can create unexpected friction points, though the current halt appears more severe in scope.
Unanswered questions
Multiple block explorers confirm the halt is real and sustained, but key details are missing. The precise block height where production stopped isn't public. It's unclear if a hotfix is imminent or if developers are still diagnosing the issue. Until an official statement comes out — and blocks start rolling again — the community is left watching the mempool grow.
