Zcash Block Explorers Go Dark for Hours After Orchard Pool Upgrade

Table of Contents Zcash, the privacy-focused cryptocurrency built on Bitcoin’s codebase, triggered concern across the crypto community on June 3, 2026. Multiple block explorers showed no new blocks after block 3,364,601, recorded at 5:27 AM UTC. Under normal conditions, the network adds a new block roughly every 75 seconds. The gap stretched beyond four hours, prompting widespread speculation that the network had gone offline entirely. Block explorers showed no new blocks for more than four hours, fueling speculation that the chain had gone offline. On-chain data platform Arkham Intel filtered the Zcash blockchain transfers table, and the results showed no transactions recorded in over five hours. The apparent halt drew significant attention from traders and on-chain analysts monitoring the network. Did Zcash go down yesterday? Zcash is a privacy-focused cryptocurrency that lets users shield transactions from public view. On Wednesday, several block explorers showed no new ZEC blocks for hours, sparking claims that the network was down. Our research team investigated what… pic.twitter.com/LxH4N4XKLU — Arkham (@arkham) June 4, 2026 Social media amplified the concerns quickly. X account Solid Intel claimed the network was “down” and had not produced blocks in four hours, with the post gaining over 180,000 views and nearly 100 retweets. “INTEL: ZCASH NETWORK IS DOWN, NOT PRODUCED ANY BLOCK IN THE PAST 4 HOURS,” the account posted on X. The report was also used, in part, to promote competing privacy coin Monero. However, contrary signals also emerged. Other websites, such as a ZEC mining pool site, appeared to show Zcash blocks continuing to be mined. This pointed to a disconnect between what block explorers were displaying and actual network activity. Helius CEO Mert Mumtaz pushed back on the outage narrative directly on X. “fyi this is completely false the network is not down. a few explorer apps are connected to a bad node, so the explorers are false. but network is fully functional,” Mumtaz wrote. He confirmed the Zcash mainnet had not crashed and that node malfunctions were behind the misleading explorer data. The timing of the outage reports coincided with a recent security patch to the network. Zebra 5.0.0 was released as an emergency soft fork, activating NU6.2 and re-enabling Orchard with a corrected circuit. The total ZEC supply was confirmed intact throughout. The soft fork had disabled Orchard transactions because a direct patch would have revealed too much information about the nature of the issue to anyone with access to the updated code. The vulnerability in the Orchard shielded pool was identified on May 29 and patched on the evening of June 1. ZODL CEO Josh Swihart provided the clearest technical explanation of what occurred. “A coordinated Zcash network upgrade was activated at block 3,364,600. Many block explorers had not yet updated their nodes at the time of the upgrade, resulting in a loss of visibility into the chain’s state,” Swihart told CoinDesk. He added that teams were actively working on node updates at the time. Several explorers and wallets may also have been out of sync during the incident, including Cake Wallet and Zodl Wallet, which could have contributed to confusion around the chain’s status. The distinction between a full network halt and a block explorer synchronization issue carries weight for assessing the actual reliability of the Zcash network.