Zcash Block Height

Key Facts

• Block height counts a block's position in the chain; the genesis block is height zero.
• The current tip can move between page generation and page load because Zcash keeps producing blocks.
• A one-block difference between observers often reflects propagation or indexing latency, not a broken chain.
• Height is public, but it does not reveal the sender, recipient, amount, or memo of a fully shielded payment.
• Confirmations count blocks added after a transaction's block and should not be confused with the block height itself.

What the block height number means

Every Zcash block has a height. The number tells you where that block sits in the ordered history beginning with the genesis block at height zero. When an explorer says the network is at a particular height, it normally means that its node or indexer currently treats that block as the tip of the best valid chain.

The Network Truth Console shows the height captured in the site's validated build-time snapshot. It also keeps the block hash and observation time beside the number. Height without a timestamp is incomplete because the network can advance while a cached page remains unchanged.

Why two explorers can show different heights

Blocks take time to propagate, nodes poll at different moments, and indexers may write data after a node has already accepted a block. During that small race, one observer can show height N while another shows N minus one. A difference of one or two blocks is not automatically evidence of a fork or outage.

A useful comparison checks more than the large headline number. Compare each observer's timestamp, block hash, reported status, and current difficulty. If the gap keeps widening or the hashes disagree at the same height, the disagreement deserves investigation instead of a green status label.

Block height and confirmations are related, not identical

A transaction receives its first inclusion when a miner places it in a block. As newer blocks extend that chain, the transaction accumulates confirmations. If a transaction is in block 100 and the current tip is 105, an interface may describe it as having six confirmations when it counts the containing block, although software conventions should always be checked.

The right confirmation threshold depends on the receiving service and the risk it is managing. Height alone cannot tell you whether an exchange has credited a deposit, whether a wallet has finished scanning, or whether a merchant considers a payment settled.

Why block times are irregular

Zcash currently targets a 75-second spacing between blocks. That is an average controlled by the proof-of-work difficulty adjustment, not a schedule. Two blocks can arrive seconds apart, and another gap can last several minutes, without violating the target.

This randomness is why estimating clock time from height requires a range, not false precision. It is reasonable to use target spacing for a rough forecast across many blocks. It is not reasonable to promise that the next block will arrive exactly 75 seconds after the last one.

What a block explorer can and cannot prove

A block record can prove public consensus data such as its height, header hash, timestamp, difficulty, transaction count, and relationship to nearby blocks. A full validator independently checks consensus rules rather than trusting the explorer's presentation.

The same record cannot expose encrypted Orchard or Sapling payment fields. A shielded transaction still has a public transaction envelope and block position, but its protected sender, recipient, amount, and memo are not made searchable just because the block height is public.

How House of Zcash publishes the tip

The site fetches node-backed ZcashInfo data on the server, validates the response, and stores the result in a static snapshot. A secondary Blockchair observation is used to compare best height and current difficulty. Browser visitors do not trigger provider requests, and the source clock remains visible.

This model favors auditability over pretending to be a streaming node. If the refresh fails, the existing validated snapshot remains in place. Readers can therefore distinguish a known older observation from a fresh but partially written response.

FAQ