Skip to content
ZcashZecZcash
Format and checksum ยท runs in your browser

Zcash Address Checker

Paste a Zcash address to see which type it is and whether its checksum is correct. Well formed does not mean funded: the checker never asks a server about your address and says nothing about balances.

Try an example:

The result appears here as you type or paste. The address you paste is not sent anywhere.

Reference

Zcash address formats at a glance

PrefixTypeEncodingDefined in
t1Transparent, P2PKHBase58CheckProtocol specification, ZIP 320
t3Transparent, P2SHBase58CheckProtocol specification
zs1Sapling shieldedBech32Protocol specification, ZIP 173
u1Unified AddressBech32m (after F4Jumble)ZIP 316
tex1Transparent-source-onlyBech32mZIP 320

The transparent version bytes are 0x1CB8 (t1) and 0x1CBD (t3) on Mainnet; Testnet P2PKH uses 0x1D25. For a plain-language explanation of what each type means for privacy, read Zcash address types explained; for how transparent and shielded transactions differ, see shielded vs transparent transactions.

What to do next

After the format check

FAQ

Questions about Zcash addresses

How do I check whether a Zcash address is valid?

Paste it into the checker above. It recognises the address type from its prefix and verifies the checksum: Base58Check for t1 and t3 addresses, Bech32 for Sapling zs1 addresses and Bech32m for Unified u1 and TEX tex1 addresses. A single wrong character fails the checksum.

Does a valid result mean the address exists or has funds?

No. It only means the string is well formed. A well-formed address can be new, unused or never funded. For a transparent address the Zcash Explorer shows its public balance and history. Shielded balances are not public, so no explorer can show them.

Is my address sent to a server?

No. The check runs in your browser and the text is not sent anywhere. To learn whether the tool is useful, the site records one anonymous event per visit with only the outcome of a check (for example valid, Unified, Mainnet), never the address.

What do the prefixes t1, t3, zs1, u1 and tex1 mean?

t1 is a transparent P2PKH address and t3 a transparent P2SH address, both public like Bitcoin addresses. zs1 is a Sapling shielded address. u1 starts a Unified Address, which can bundle several receiver types. tex1 is a transparent-source-only address that accepts funds only from transparent addresses.

Why does the checker not decode the receivers inside a Unified Address?

A Unified Address hides its receivers behind an extra scrambling step (F4Jumble) defined in ZIP 316. The checker verifies the outer Bech32m checksum, which catches typing mistakes, but it does not open the address. Use your wallet to see which pools an address can receive in.

Why does a Sprout address show 'Not checked'?

Legacy Sprout addresses (prefix zc) are only matched by pattern here, without a checksum check. Sprout is the oldest shielded pool and new funds should not use it.

Sources: Zcash Protocol Specification (address encodings), ZIP 316 (Unified Addresses), ZIP 320 (TEX addresses), BIP 173 and BIP 350 (Bech32, Bech32m). Test vectors from the zcash-test-vectors repository were used for the Unified examples. Read October 14, 2026.

Talk Zcash addresses with the community

Join ZecZcash, our independent Zcash community on Telegram, for real-time news, price talk and discussion.

Join @ZecZcash on Telegram