Zcash Explorer Guide: How to Check Transactions, Blocks and Addresses

A blockchain is a public, shared ledger — and a block explorer is simply a tool that reads that ledger and shows you what's on it, in a form a person can actually use. If you've never used one before, this guide walks through exactly how to check a Zcash transaction, block, or address using the ZecZcash Explorer — our own independent block explorer — and, just as importantly, what Zcash's privacy design means an explorer genuinely can't show you.

What is a Zcash block explorer?

Every Zcash transaction that has ever been confirmed lives inside a block, and every block is chained to the one before it, all the way back to Zcash's October 2016 genesis block. That chain of blocks is the blockchain — a complete, public record that anyone can independently verify. A block explorer reads that record directly and presents it as something searchable: paste in an identifier, and it shows you the matching transaction, block, or address.

ZecZcash runs its own Zcash Explorer, independent of any exchange or wallet provider. It reads live from the Zcash blockchain, and it works the same way for anyone — you don't need an account, a wallet connection, or any of your own keys to use it.

What can you search?

The Explorer's search box accepts six kinds of input:

• Transaction ID (TXID) — the identifier for one specific transaction
• Block height — a block's position in the chain, e.g. 3488799
• Block hash — a block's own unique identifier
• Transparent address — a t1 or t3 address
• Shielded address — a zs1 (Sapling) address
• Unified Address — a u1 address, which can contain shielded receivers

Transaction, block, and transparent-address searches return real on-chain detail. A shielded or Unified address search confirms the address is validly formatted, but — as covered in detail below — it can't return a balance or history, because that data isn't public in the first place.

How to check a Zcash transaction

1. Find the TXID. Your wallet or exchange shows this in your send confirmation or transaction history, usually labeled "transaction ID," "TXID," or "transaction hash." It's a long string — copy the whole thing.
2. Open the Zcash Explorer.
3. Paste the TXID into the search box and press Search.
4. Read the result. For any transaction, you'll see:
   • Confirmation status — confirmed or unconfirmed, and the confirmation count once it's mined
   • Block — which block it's included in, linked to that block's own page
   • Value flow — what value moved, described carefully (see "Understanding inputs and outputs" below — this is deliberately not a simple "sender sent X to recipient" statement)
   • Fee — the network fee paid, when it can be determined
   • Transparent inputs & outputs — for any transparent portion of the transaction
   • Shielded pool activity — for any shielded portion, limited to what Zcash's privacy design makes public (see the comparison table below)

If the Explorer shows your transaction confirmed but your wallet still hasn't reflected it, that's usually a wallet-side sync issue rather than anything wrong on-chain — the Zcash wallet troubleshooting guide walks through the specific symptoms.

How to check a Zcash block

Search a block height (like 3488799) or a block hash directly. A block page shows:

• Height and timestamp
• Confirmations — how many blocks have been added since
• Transaction count and the list of transaction IDs it contains
• Block size and difficulty
• Previous/next block navigation, so you can browse the chain
• Technical details — block hash, Merkle root, version, bits, and nonce, for anyone who wants the full protocol-level record

Only fields the Explorer's data source actually provides are shown — nothing here is estimated or inferred.

How to check a Zcash address

Search a transparent (t1/t3) address to see:

• Current balance
• Total received and total sent — lifetime totals for the address
• Transaction count
• Transaction history — one entry per transaction this address was part of, showing a net balance change for each. This is deliberately not labeled "sent" or "received" per transaction: a single Zcash address can appear as both an input and an output of the very same transaction (for example, when change returns to it), so the honest, provable figure is the net effect on that address's balance, not an assumed direction.
• Unspent outputs — the specific transparent outputs currently available to be spent from this address

This is the practical answer to "check Zcash wallet balance" or "Zcash wallet balance checker" — for a transparent address, the Explorer is a wallet balance checker, reading the same public data your own wallet would.

This does not extend to shielded or Unified addresses. See the next section.

Why can't I see a shielded Zcash balance?

This is not a missing Explorer feature, and it isn't unique to ZecZcash's Explorer — no block explorer can show a shielded Zcash balance. It's a deliberate, core property of how Zcash's shielded pools work.

A transparent address works like a public ledger entry: its balance and history are stored directly on-chain, in the clear, for anyone to read — that's what makes a transparent-address lookup possible at all. A shielded transaction is built differently on purpose. It uses zero-knowledge proofs to let the network verify the transaction is valid — no double-spending, correct amounts — without revealing the sender, recipient, or amount to anyone but the participants. The blockchain publicly shows that a shielded transaction happened, but nothing on-chain links that activity to a specific shielded address the way a transparent transaction links to a t1 address.

That's why searching a shielded or Unified address here only confirms it's a validly formatted Zcash address — the Explorer isn't withholding a balance it has access to; the balance simply isn't public data to begin with. For the fuller technical picture, see our Zcash privacy page and Shielded vs. Transparent Zcash Transactions Explained. For how much ZEC sits in Zcash's shielded pools in aggregate — a network-wide total, never tied to any individual address — see the Shielded Supply Tracker.

Transparent vs. shielded Explorer data

A note on that shielded action count row: Orchard and Ironwood actions are protocol objects, and a real spend or output can be indistinguishable from a placeholder by design — so an action count doesn't directly tell you how many real payments happened, or who was involved.

Understanding inputs and outputs

A Zcash transaction is not the same shape as a bank transfer, and it's easy to over-read what an input or output address actually proves. The plain version: inputs are the coins a transaction spent; outputs show where those coins went. That's it — an input isn't automatically "the sender" in any personal sense, and an output isn't automatically "the recipient."

Two things make this genuinely different from a simple A-sends-to-B model:

Multiple inputs and outputs. A single transaction can spend several inputs at once (combining smaller amounts to cover a payment) and pay out to several outputs at once (one to the actual recipient, others elsewhere). Nothing in the public data pairs a specific input with a specific output — you can see the full set of both, and the total, but not which input "funded" which output.

Change outputs. Zcash transparent addresses work on an unspent-output model: if you spend a 10 ZEC output to pay someone 3 ZEC, the difference doesn't get "kept" in place — a new output sends the leftover 7 ZEC (minus the fee) back to an address you control, often a fresh one. An output that returns value to an address already used as an input in the same transaction is a common pattern for this kind of wallet change — but Zcash's public data doesn't prove that was the actual intent, so the Explorer flags it as a possible pattern, never a certainty.

This is exactly why the Explorer avoids blunt "sender = input address" or "recipient = output address" language, and why an address's own transaction-history row is labeled a net balance change rather than "sent" or "received" — those are the statements the public data can actually support.

What are confirmations?

When a transaction is included in a block, it has one confirmation. Each additional block added on top of that one adds another confirmation — so a transaction in the most recent block has one confirmation, and one ten blocks back has ten. More confirmations mean the transaction is buried under more accumulated proof-of-work, making it progressively less practical to reverse.

There's no single number that's universally "safe" for every situation — how many confirmations are enough depends on the value involved and who's asking (many exchanges publish their own specific threshold for crediting a deposit, for instance). We're not going to invent a one-size-fits-all number here; if you're waiting on a specific deposit, the receiving service's own stated requirement is the number that actually applies.

ZecZcash Explorer privacy

Beyond that: searching here doesn't require a wallet connection, an account, or any personal information. A transparent address search shows exactly the data that's already public on the blockchain — nothing more. A shielded or Unified address search, as covered above, can't return private data because that data was never public to begin with; Zcash's protocol rules protect it regardless of what any explorer tries to do.

Start exploring

The best way to understand a block explorer is to use one. Open the Zcash Explorer and try it with a transaction ID from your own wallet, or a recent block height — everything above will make a lot more sense once you're looking at a real result.