Zcash / transaction
Zcash transaction lookup
Look up any Zcash transaction on Zcash Block Explorer. tx.taxi detects the format, picks the right Zcash explorer, and redirects.
Zcash has two address families that behave very differently in an explorer. Transparent addresses (t-addrs) start with t1 for P2PKH or t3 for P2SH and behave like Bitcoin UTXOs: balances and history are public and queryable. Shielded addresses start with zs1 (Sapling) or u1 (Unified) and use zero-knowledge proofs to hide the sender, recipient, and amount on-chain - they are not browsable by address in the same way transparent addresses are. Paste a Zcash value at tx.taxi/{value} and the router classifies the format and 302-redirects to the Zcash Block Explorer. Shielded addresses route to the explorer but the explorer cannot show their transaction history. On this page: Zcash transaction lookups specifically.
How it works
- Copy your
Zcash transaction(e.g. the transaction hash from your wallet). - Paste into the search above or visit
tx.taxi/<your-transaction>directly. - tx.taxi detects the Zcash format and redirects to Zcash Block Explorer.
Frequently asked questions
What is the difference between t-addrs and z-addrs on Zcash?
Transparent (t1, t3) addresses behave like Bitcoin: public balances, public history, fully visible on a block explorer. Shielded (zs1, u1) addresses use zero-knowledge proofs so the sender, recipient, and amount are encrypted on-chain.
Can a Zcash explorer show shielded balances?
No. Shielded balances are not visible to anyone without the holder's viewing key. A block explorer can show that shielded transactions exist and aggregate pool sizes, but it cannot show per-address shielded history.
What is a Unified Address on Zcash?
A Unified Address (u1-prefixed) bundles receivers for multiple Zcash address types into one shareable string. The wallet picks the best receiver based on what the sender supports, preferring shielded receivers when possible.