Deshield responsibly
One deshield reveals little. A pattern reveals a lot: 10 ZEC to the same address every hour for a day tells the world how much you hold, when you're active, and where your coins end up. Sort the table by Times seen to spot the patterns yourself.
Recent deshields
One row for each transparent address that received ZEC in a deshielding transaction. Times seen is how many deshields that same address received in this window.
| Transaction | ||||
|---|---|---|---|---|
×3 This address received 3 deshields in this window. Tap it to see only that address.
mixed The transaction also spent transparent ZEC, so part of this amount may not have come from a shielded pool.
The same 240 ZEC, two ways
✗ Easy to follow
- 10 ZEC every hour, for 24 hours
- Always to the same transparent address
- Same round amount each time
- Anyone can see a 24-deshield pattern adding up to 240 ZEC, and your daily schedule
✓ Much harder to follow
- Pay a shielded or unified address directly when the recipient accepts one, so nothing becomes public
- When you must deshield, use a new transparent address each time
- Deshield only what you need, when you need it, with no fixed schedule or amount
How to deshield without giving yourself away
🛡 Stay shielded when you can
The best deshield is the one you don't need. Many wallets and services accept shielded or unified addresses. Paying them directly keeps the amount and both parties private.
🔄 Use a fresh address each time
Reusing one transparent address ties all of its deshields together. Many modern wallets can create a new transparent address for each use. Let them.
🎲 Avoid schedules and repeated amounts
Regular timing and identical amounts form a fingerprint even across different addresses. Deshield only what you need, when you need it.
🔍 Don't round-trip exact amounts
Shielding 13.48291 ZEC and deshielding 13.48291 ZEC soon after lets an observer match the two by amount and timing, even though the shielded part stayed private. Let funds sit shielded and move different amounts.
What this page does and doesn't show
✔ Only public data
Every row comes from the transparent side of a deshielding transaction, read directly from our own Zebra node. Anyone running a node can see exactly the same thing.
✘ No guesses about owners
AtlasZEC never labels who owns an address and never tries to trace shielded activity. Times seen counts how often one public address appears here, nothing more.