The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →To confirm whether a Zcash transaction used a shielded pool, inspect its transaction-level details in the wallet that sent or received it. For a Zcash node wallet, z_viewtransaction "<txid>" can show shielded spends and outputs labeled Sprout, Sapling, or Orchard. The standard gettransaction result does not provide complete shielded-component details.
Check the transaction in the wallet that knows about it
Start with the wallet that sent or received the funds and locate the transaction ID (txid). A wallet’s transaction-detail screen may identify the pools used, but labels and available details differ by wallet. Do not assume that a particular icon, address format, or abbreviated summary establishes the pool for a specific transaction.
| # | 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 |
As an Amazon Associate I earn from qualifying purchases.
The documented node RPC methods below provide a more explicit route when the transaction is in that wallet’s data. They are not described as general public lookup services for arbitrary txids.
Use Zcash node RPCs for pool-level details
1. Retrieve the wallet transaction
Run gettransaction "<txid>" in the Zcash node wallet. This returns in-wallet transaction details, but the RPC documentation says it omits complete shielded components. A result from this command alone may therefore be insufficient to determine whether shielded spends or outputs were involved. See the Zcash 6.12.2 gettransaction RPC documentation.
2. Request shielded transaction details
Run z_viewtransaction "<txid>". Its response can include shielded spends and outputs and identify the relevant pool as Sprout, Sapling, or Orchard. A shielded spend or output listed there is direct evidence of activity in that shielded pool. See the Zcash 6.12.2 z_viewtransaction RPC documentation.
3. Check received-payment records when applicable
If your wallet tracks a received payment by address, z_listreceivedbyaddress returns records with a pool field. Documented values include transparent, sprout, sapling, and orchard. A shielded pool value establishes the pool for that received component; a transparent value establishes that the particular received component is transparent. It does not, by itself, characterize every component of a mixed transaction. See the Zcash 6.12.2 z_listreceivedbyaddress RPC documentation.
How to interpret the result
- Shielded activity: The transaction detail lists a shielded spend or output in Sprout, Sapling, or Orchard, or the relevant received-payment record identifies one of those pools.
- Transparent component: A record explicitly labeled
transparentsupports calling that component transparent. Do not extend that conclusion to other components without checking them. - No shielded details shown: This is not proof that a transaction had no shielded activity unless the data source and its coverage establish that. In particular, a missing breakdown in a public explorer is inconclusive: the cited RPC documentation describes wallet-scoped data and does not establish what every explorer displays.
Why an address or wallet icon is not enough
A Zcash transaction can include transparent and shielded components, so the fact that it is a Zcash transaction does not settle which pools it used. Unified addresses can encode multiple receiver types; the address format alone is not transaction-level evidence. The official explanation notes that a unified address is generated from multiple Zcash address types and, with features such as autoshielding, can enable shielded-by-default transactions in supporting wallets. Read Zcash’s explanation of unified addresses alongside the Zcash protocol specification.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Wallet behavior also varies: official guidance describes wallets that shield by default, wallets that let users choose, and wallets limited to transparent transactions. A wallet’s brand, its default setting, or a shield icon cannot substitute for transaction-level pool details.
Report the finding precisely
Describe what the data actually shows—for example, “the wallet details list an Orchard shielded output” or “the received component is labeled transparent.” Avoid saying that a transaction is wholly hidden or that its user has complete anonymity merely because it includes a shielded component. Pool activity is a specific transaction fact, not a blanket statement about what information is visible.
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.
