iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Use a shielded transaction whenever the recipient’s wallet or service supports shielded receiving and you want the amount and counterparties kept out of public blockchain data. Use a transparent transaction only when a recipient, exchange, accounting process or audit requirement explicitly needs a t-address. A transparent t-to-t payment publishes the sender, receiver and value. A fully shielded z-to-z payment encrypts those fields while proving that the transaction is valid. Mixed t-to-z and z-to-t payments protect only part of the flow and can still expose useful linkages.
What the two transaction types reveal
Zcash gives you two address families with different visibility rules. Transparent addresses begin with t; shielded addresses are commonly called z-addresses. Your privacy outcome depends on the address types at both ends of the payment, not merely on owning a wallet that supports shielded funds.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Cryptocurrency: Turn $20.00 In To $20,000: The Ultimate Beginner’s Guide About Blockchain Wallet,... | $2.99 | Buy on Amazon |
| Flow | What is visible on the public chain | Typical reason to use it |
|---|---|---|
| Transparent t-to-t | Sender address, recipient address and transferred value are public, much like a Bitcoin transaction. The transaction itself, fee and other public metadata can be inspected by anyone. | The destination requires a t-address, or public auditability is intentional. |
| Transparent-to-shielded t-to-z | The transparent input and its value are public. The shielded recipient side is not exposed in the same way. | Moving funds from a transparent source into shielded funds. |
| Shielded-to-transparent z-to-t | The transparent destination and amount received are public. The shielded source is not displayed as a normal public sender address. | Paying a service that can receive only at a t-address. |
| Shielded z-to-z | Sender, recipient and value are encrypted while the network verifies validity. Fees remain public, and outside information can still create linkages. | Private person-to-person payments, donations or transfers when both sides support shielded receiving. |
The practical distinction is confidentiality, not invisibility. A shielded transaction can still be known to have occurred, and the public fee does not disappear. If an amount, transaction ID, memo, timing or counterparty detail is disclosed elsewhere, observers may be able to connect that information to on-chain activity.
What “shielded” does—and does not—mean
Fields protected in a z-to-z payment
In a fully shielded flow, the protocol encrypts the sender, recipient and value while providing cryptographic proof that the transaction follows the rules. Observers can validate the transaction without receiving those details in clear text. This keeps ordinary chain viewers from reading the payment’s counterparties and amount directly.
Information that remains public
- The network fee is public.
- The existence of a transaction can be observed even when its participants and value are concealed.
- Transparent inputs or outputs in a mixed transaction remain visible.
- Information you reveal to a recipient, exchange, donor, accountant or other party can be used to associate your real-world activity with a shielded transaction.
For that reason, describe shielded payments as private or confidential on-chain, not as completely anonymous. Privacy can be weakened by operational mistakes, required transparent legs, or disclosure outside the blockchain.
How address choice changes the decision
Transparent addresses (t-addresses)
A t-address is appropriate when the destination explicitly asks for one or when a public record of incoming and outgoing value is part of the workflow. An exchange may assign a deposit address that starts with t; a merchant’s point-of-sale system or an accounting process may likewise accept only transparent addresses.
The cost of that compatibility is visibility. A t-to-t payment reveals both addresses and the amount. Anyone able to inspect the chain can follow that transaction and connect it with other activity associated with those addresses.
Shielded addresses (z-addresses)
A z-address is the choice when both wallets or services support shielded receiving and you want the payment details kept confidential on-chain. This is generally the best fit for personal transfers, private donations and routine payments where there is no requirement for public amount-level auditability.
Unified addresses
Some wallets expose a unified address that can represent more than one receiver type behind a single destination. Where supported by both the sending wallet and the recipient’s software, a unified address can improve interoperability: the sender does not have to guess which receiver pool the recipient prefers. It does not make every resulting transaction fully shielded automatically. Confirm what the wallet will select and whether the recipient’s service actually supports unified addresses before sending.
Recipient compatibility is the first practical check
You cannot choose privacy in isolation from the destination. Wallet behavior varies: one wallet may shield every transaction, another may offer a private-or-transparent choice, and another may support only transparent transactions. Zcash user guidance warns that a wallet allowing only transparent transactions exposes all wallet and transaction information to a public blockchain.
Exchanges and other custodial services often publish an exact deposit-address format. If the service gives you only a t-address, a z-to-z payment cannot arrive there as a shielded receive; you need a transparent destination leg. If it supplies a shielded or unified receiving option, follow the service’s current instructions rather than assuming that every account or asset network has the same capability.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute- Ask the recipient for the exact address or payment request, not merely “your Zcash address.”
- Check whether the destination accepts shielded funds, transparent funds, or both.
- For a unified address, verify that your wallet version supports sending to it and learn which receiver it will choose.
- Confirm any memo, reference number or compliance field separately; a memo may identify a payment even when on-chain amounts and addresses are shielded.
Support changes as wallets, exchanges and address formats are updated. Recheck the destination’s current documentation immediately before a significant transfer.
Decision guide: which should you use?
| Your situation | Recommended flow | Why | Main trade-off |
|---|---|---|---|
| Private payment to a person whose wallet accepts shielded receiving | z-to-z | Keeps sender, recipient and value out of ordinary public-chain data. | Both wallets must support the shielded flow; external disclosures can still create linkages. |
| Donation where the recipient accepts a shielded address | z-to-z | Protects the donor and amount from routine public inspection. | The recipient may still know your identity from the donation channel or memo. |
| Transfer to an exchange that provides only a t-address | z-to-t, if your wallet supports it | Meets the destination’s address requirement. | The transparent destination and received amount become public. |
| Payment to a merchant or service that requires a t-address | Transparent output, using the wallet’s supported route | Ensures the merchant can credit the payment. | Public observers can inspect the transparent side. |
| Bookkeeping or grant process that deliberately needs public auditability | t-to-t | Anyone can verify the addresses and amount on-chain. | There is little on-chain confidentiality. |
| Destination’s capabilities are unclear | Pause and verify; do not guess | Address-type mistakes can delay or strand funds. | Requires an extra compatibility check before sending. |
For ordinary private payments, the default should be shielded-by-default when the recipient supports it. Transparent is a compatibility or auditability choice, not a privacy upgrade.
Step-by-step checklist before you send
- Identify the destination type. Inspect the full address or payment request and determine whether it is transparent, shielded or unified. Do not rely on a shortened display, a contact name or a copied label.
- Read the recipient’s current requirements. Exchanges, merchants and custodial wallets may restrict deposits by address type, network or account. A service that accepts Zcash in general may still require a t-address for your particular deposit route.
- Inspect your wallet’s send options. Look for labels such as private, shielded, transparent or unified. Some wallets automatically shield; some let you choose; some expose only transparent sending.
- Choose the least-exposing compatible route. If both sides support shielded receiving and confidentiality matters, select z-to-z. If the destination requires a t-address, use the required transparent leg and assume its address and amount will be public.
- Check the amount and fee separately. Shielding does not hide the fee. Make sure the wallet shows enough spendable balance in the relevant pool and that you understand whether a conversion between transparent and shielded funds is part of the transaction.
- Handle memos and references carefully. A memo can be necessary for an exchange or donation account, but it may reveal who the payment concerns. Enter only the required information and keep a private record of what you disclosed.
- Send a small test when the destination allows it. This is especially sensible for a new exchange, unified address or unfamiliar wallet. Wait for the recipient to confirm credit before moving the remainder.
- Save the transaction ID and receipt privately. The ID can help resolve support issues. Sharing it publicly, along with the amount or counterparty, can reduce the practical privacy you expected.
Mixed transactions: useful, but not fully private
A t-to-z transfer is commonly used to move value from a transparent balance into the shielded pool. The transparent sender and amount remain visible, so an observer can see that funds entered a shielded destination even though the shielded recipient details are not displayed as a normal address.
A z-to-t transfer works in the opposite direction when a service requires a transparent deposit. The destination and amount become public. Timing, amount and known exchange-deposit information may allow an observer to associate the transparent output with the earlier shielded activity.
Do not describe either mixed flow as equivalent to z-to-z. The shielded side protects some fields, but the transparent side supplies an observable anchor that can support analysis or real-world linkage.
Privacy, compatibility and auditability compared
| Criterion | Shielded z-to-z | Transparent t-to-t | Mixed t-to-z or z-to-t |
|---|---|---|---|
| On-chain privacy | Highest of the three for sender, recipient and value, subject to disclosure outside the chain. | Lowest; sender, recipient and value are public. | Partial; transparent-side details remain public. |
| Recipient compatibility | Requires a shielded-capable destination. | Broad where services require or support t-addresses. | Useful when only one side supports shielded receiving. |
| Public auditability | Limited for counterparties and amounts; validity is still proven by the protocol. | Strong; observers can inspect the public transfer. | Strong on the transparent side, limited on the shielded side. |
| Operational complexity | Can require compatible wallet versions, shielded balances and recipient support. | Usually simplest when the destination specifies a t-address. | Requires understanding which leg is exposed. |
| Linkability risk | Fees, disclosed transaction IDs, amounts, timing and counterparties can create links. | Addresses and values provide direct links for chain observers. | Transparent inputs or outputs can connect otherwise private activity. |
Common failure modes and what to do
The recipient says the payment is missing
First compare the address type you used with the destination’s stated requirement. Confirm the transaction ID, amount, network and required memo. If you sent to a t-address, the recipient may need ordinary confirmation time or manual crediting. If you sent a shielded payment to a service that accepts only transparent deposits, contact that service’s official support with the transaction details; do not send a second payment until the first is resolved.
The wallet offers no shielded option
That wallet may support only transparent transactions, or the current account may not have shielded capability enabled. Do not assume that a Zcash balance is private merely because the asset is ZEC. Use a wallet and destination combination that explicitly supports the shielded flow, or proceed transparently only after accepting the public-visibility consequence.
A unified address is rejected
Unified-address support is not universal. Verify that both the sender wallet and receiving service support the format and that you copied the complete address. If the service documents a separate t-address or z-address, use the documented format instead of repeatedly retrying an unsupported unified address.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →You need proof of payment
A shielded transfer can be valid without exposing its amount and counterparties to everyone. Provide the recipient with the transaction ID or other wallet-generated proof only through a private channel, and share the minimum information required for reconciliation. Publishing those details can undermine the confidentiality you sought.
What wallets may do automatically
Wallet interfaces are not consistent. According to Zcash guidance, a wallet may shield all transactions, offer a private-or-transparent choice, or allow only transparent transactions. Read the confirmation screen rather than inferring behavior from a general “send ZEC” button.
- Shield-all behavior: convenient for privacy, but a transparent-only destination may require a separate supported route or may be incompatible.
- Choice-based behavior: gives control, but you must select the correct receiver and understand which side is public.
- Transparent-only behavior: maximizes compatibility with t-address destinations while exposing wallet and transaction information on the public blockchain.
Wallet updates can change defaults, labels and unified-address support. Recheck the current version’s documentation and the destination’s instructions before a high-value transfer.
When transparent transactions are the right choice
Transparency is not inherently an error. Choose it deliberately when a recipient requires a t-address, when a public accounting trail is part of the purpose, or when your operational environment cannot safely support shielded receiving. A transparent payment can be easier for auditors, merchants and custodians to verify because the amount and addresses are directly inspectable.
The decision becomes problematic only when users select transparent by habit while expecting shielded confidentiality. Before confirming, ask: “Would I be comfortable with this address, amount and transaction history being readable on a public explorer?” If the answer is no, stop and find a compatible shielded route rather than assuming privacy will be added later.
When shielded transactions are the right choice
Use z-to-z for ordinary private transfers, donations and payments where both wallets support shielded receivers and keeping amounts and counterparties out of public-chain data matters. Keep in mind that the recipient may still know who paid through an invoice, account login, delivery address, memo or conversation. Shielded technology protects blockchain fields; it does not erase information you voluntarily provide elsewhere.
Frequently asked questions
Can an exchange receive shielded ZEC?
Only if that exchange and the specific deposit route support shielded receiving. If it provides only a t-address, you need a transparent destination leg and should expect that address and amount to be public. Verify the exchange’s current instructions because support can change.
What does a t-address reveal?
In a t-to-t transaction, the sender address, recipient address and value are publicly visible, similar to Bitcoin. A transparent side of a mixed transaction also reveals its relevant address and value.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallAre shielded transactions completely anonymous?
No. Shielded transactions hide sender, recipient and value from ordinary public-chain viewing, but fees remain public, the transaction can be known to have occurred, and leaked IDs, amounts, timing or counterparty details can create linkages.
Is a z-to-t payment private?
It is only partially private. The shielded source is not shown as a normal public sender address, but the transparent destination and amount are public and may help connect the payment to other activity.
Should I always use a unified address?
Use one when the recipient and your wallet both support it and the destination’s instructions allow it. A unified address can improve interoperability, but it does not guarantee that every payment will be fully shielded.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
