ZEC View
English简体中文

Zcash privacy

Zcash Shielded Transactions: How They Work

Quick Answer

Zcash shielded transactions use privacy-preserving protocols to protect financial information, unlike transparent transfers that publish it on the ledger. Holding ZEC does not automatically mean a payment is shielded. Check the transaction type and the wallet’s supported receivers; a Unified Address alone does not certify the privacy of every transfer.

Key Takeaways

  • Holding ZEC does not automatically make a transfer shielded.
  • Shielded and transparent transfers have different disclosure properties.
  • Check the wallet’s receiver and transfer support before sending funds.

Before sending ZEC

Check the actual transfer path, selected receiver and wallet release before confirming. Shielded does not mean absolutely anonymous.

What is public in the four transfer types?

These are simplified single-path payments, not a guarantee for mixed-input, multi-recipient or cross-pool transactions. “Public” means visible on the blockchain, not necessarily linked to a real name.

Ordinary ZEC payments: transparent and shielded visibility
Transfer typePublic on-chain informationProtected shielded information
Transparent → transparent (t → t)Transparent input references, sending and receiving addresses and amounts are public. The public transaction graph can be followed.No shielded protection for these transparent inputs or outputs.
Transparent → shielded (t → z; shielding)Transparent inputs, their addresses and values remain public; the net amount entering the shielded pool is public. Shielding does not erase earlier transparent history.The shielded receiving address and encrypted memo are not public. A public pool-entry amount is not a public list of shielded recipients.
Shielded → transparent (z → t; deshielding)The transparent receiving address and output amount are public, as is the net value leaving the shielded pool.The shielded source address and its prior shielded payment history are not directly published by this transfer.
Shielded → shielded (z → z)The transaction exists publicly, with its transaction ID, block inclusion, fee and protocol structure. If it crosses shielded pools, public value balances reveal net pool-crossing amounts.In a same-pool payment without transparent inputs or outputs, shielded sender and recipient addresses, the payment amount and encrypted memo are not public.

All four types leave a public transaction record and fee. Net pool movement is not always the amount paid to one recipient: change, fees and multiple outputs can differ. Mixed transactions retain their transparent disclosures; coinbase outputs have special visibility rules. Sources: Zcash documentation: transaction types and ZIP 315: information revealed by transactions (Draft guidance, not proof of wallet implementation).

Receiving address and wallet compatibility checklist

  • Confirm the recipient and network. Obtain the current address through a trusted channel, compare the full address in the wallet and confirm Zcash mainnet versus testnet. Do not guess support from an address prefix.
  • Check both ends. Verify the sender can send to the recipient’s receiver and pool, and the recipient’s installed release and platform can receive and spend that payment. Recognizing a Unified Address does not mean supporting every receiver inside it.
  • Inspect the confirmation screen. Check the selected receiver, source funds, any transparent outputs or fallback, pool crossing, fee and privacy warnings. If the wallet does not make the path clear, stop and check its current official documentation.
  • For an exchange or service, read its deposit rules. Confirm the supported receiver, minimum deposit, required confirmations and any memo or transparent-source requirement with the service. A valid address is not a guarantee of account credit.

Risks beyond the public blockchain

  • On-chain public information: transparent addresses and amounts, pool-boundary values and timing can support correlation. A transparent address alone is not a verified real identity.
  • Transaction-end records: the sender, recipient, exchange or wallet service may retain payment details, account identity and network or device records. Shielding does not delete those records or protect a compromised device.
  • Active disclosure: sharing a viewing key, receipt, screenshot or payment details can reveal information. Incoming and full viewing keys have different scopes; never send this site a seed, spending key or viewing key.

Next step: Compare documented wallets and current support → Then confirm compatibility in the wallet publisher’s current release documentation. This directory is not a wallet certification or a recommendation to send funds.

Official sources checked and scope

Checked 2026-10-09. The basics page supplies the four-type explanation; its older fee, address-prefix and wallet-market statements are not treated as current guidance. ZIP 315 remains Draft. ZIP 316 separates Active Revision 0, Withdrawn Revision 1 and Draft Revision 2; draft requirements are not claims about installed wallets.

Shielded vs transparent transfers

The z.cash explanation describes a choice: financial information can be shielded or transparent. This establishes a transaction-type distinction, not a guarantee that every wallet workflow uses the shielded path.

Before relying on privacy, a reader needs to identify the actual wallet capability and transaction type. This guide does not inspect real addresses or infer a person’s activity.

What this explanation does not prove

The educational page alone does not establish immunity from all observation, endpoint compromise or user disclosure. Nor does a balance in a shielded pool prove how many distinct people use it.

We keep those questions separate rather than extend a short educational statement into an absolute anonymity promise. Exact protocol field visibility, viewing-key permissions and address types require the corresponding specification evidence; the address-type, viewing-key and protocol reference guides now preserve those source scopes, without device or activation certification.

Check the transfer and wallet

Use the sending checklist above to compare transaction visibility and compatibility. Official sources for the checklist were retrieved on 2026-10-09, separately from the original educational snapshot on 2026-10-01; retrieval is not a publication date or wallet audit date.

Explore shielded pool data

The network dashboard measures source-reported value balances. It cannot measure the quality of privacy, determine identities or certify a wallet setup.

Wallet DB now provides a limited source-stated capability corpus and current publisher warnings; complete released-version coverage and device validation remain open. No tool on this site receives seed phrases, private keys or viewing keys.

FAQ

Is every Zcash transaction shielded?

No. The educational source explicitly distinguishes shielded and transparent Zcash. A blanket statement that all ZEC activity is private would erase that distinction.

Does a shielded balance prove an anonymity set size?

No. A value balance is not a user count. This guide has no measurement or source establishing a one-to-one relationship between pool balances and people.

Sources and Methodology

Page updated: . Source observation dates remain separate.

The page update is an editorial date. The sending-checklist sources remain checked on 2026-10-09 and the original educational snapshot on 2026-10-01; neither is a wallet audit date.

Methodology and technical limitations

Method and limits

This guide combines official educational material with receiver and transaction-disclosure documentation. The sending checklist is educational, not a test of an installed wallet or an individual transaction. ZIP 315 is Draft guidance; ZIP 316 revision labels remain separate. Source retrieval and snapshot hashes support provenance, not absolute anonymity or device certification. No personalized privacy, evasion or investment recommendations are given.

Source dates describe the referenced observation or document, not a live price. How data is checked · Corrections