transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
e9e3a6b979dd2e5543c91cf37bc9baa00ca3f870191112039e00e9bcaac22d8aPublic counts derived from this transaction's structure. Shielded entries are counted, but their parties, amounts, and memos stay private.
| Input | Prevout | Value |
|---|---|---|
| vin 0 | transparent prevout | 0.21113115 ZEC |
| vin 1 | transparent prevout | 0.14172489 ZEC |
| vin 2 | transparent prevout | 0.14000505 ZEC |
| vin 3 | transparent prevout | 0.13747248 ZEC |
| vin 4 | transparent prevout | 0.13703929 ZEC |
| vin 5 | transparent prevout | 0.13658744 ZEC |
| vin 6 | transparent prevout | 0.13144944 ZEC |
| vin 7 | transparent prevout | 0.12680203 ZEC |
| vin 8 | transparent prevout | 0.12665795 ZEC |
| vin 9 | transparent prevout | 0.12045080 ZEC |
| vin 10 | transparent prevout | 0.11996221 ZEC |
| vin 11 | transparent prevout | 0.11804759 ZEC |
| vin 12 | transparent prevout | 0.11670469 ZEC |
| vin 13 | transparent prevout | 0.11358756 ZEC |
Input values are read from the upstream prevout index. When a value is unavailable, the upstream has not finished resolving the spent outpoint; the input still exists, but its zatoshi amount is not yet cached. Transparent outputs and full script bodies are scheduled for a follow-up consumer integration phase.
Actual fee paid by this transaction, recovered by looking up its transparent inputs. The minimum recommended fee is shown alongside for context.
Zexplorer never knows whether you sent or received any shielded portion of this transaction. If a payer provided a ZIP-311 payment disclosure, you can verify it against the public chain facts above. Disclosure payloads are processed once, never persisted, and never logged.
verify a payment disclosure →Disclosure verification is capability-gated on the upstream node (explorer.payment_disclosure.verify_v1). The tool will show an explicit "unavailable on this node" state when the operator hasn't enabled the verifier.