Zcash (ZEC) Network Shutdown Is False, Says Helius CEO With Proof

Reports that the Zcash network stopped producing blocks for more than four hours appear to have been overstated, with developers and ecosystem participants pushing back against claims of a full network outage.

The initial concern emerged after Zcash block explorer data appeared to show the latest block at height 3,364,601, with a timestamp of 05:27:48 on June 3, 2026. At the time the page was viewed, that block appeared to be roughly four hours old, while several preceding blocks were also listed as having been produced around five hours earlier. This led to claims that Zcash had halted block production.

Outage narrative is false

Helius CEO Mert said on X that the Zcash network was not down, suggesting that the report was based on faulty data or a bad node connection. Another user, Railgoon, said the situation was tied to prior action by Zcash miners and developers involving the Orchard shielded pool, which reportedly accounts for around 30% of $ZEC.

According to Railgoon, the Orchard pool had been frozen to prevent a potential bug from being exploited before a fix was released. The network then underwent a hard fork, after which normal operations resumed. In that framing, the incident was not a conventional chain halt, but a partial and intentional restriction affecting a specific shielded component of the network.

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.

Zcash processing halts

The distinction matters. A full network halt would imply that Zcash itself stopped processing blocks, a serious reliability issue for any blockchain. A temporary freeze of a specific shielded pool, especially if coordinated to prevent exploitation, points to a very different scenario: emergency containment followed by recovery.

For now, the stronger interpretation is that Zcash did not suffer a complete network outage. Instead, block explorer and wallet synchronization issues, combined with prior defensive action around the Orchard pool, likely created the appearance of a broader halt.