transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
a0d35a8d69d78790bf8abe1c45a12e28e562f65f27c99865bed975ec588ed1bcPublic 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 | 20.01680616 ZEC |
| vin 1 | transparent prevout | 62.60730590 ZEC |
| vin 2 | transparent prevout | 16.27356629 ZEC |
| vin 3 | transparent prevout | 62.57267772 ZEC |
| vin 4 | transparent prevout | 16.26831826 ZEC |
| vin 5 | transparent prevout | 62.53987422 ZEC |
| vin 6 | transparent prevout | 17.53562688 ZEC |
| vin 7 | transparent prevout | 18.76895112 ZEC |
| vin 8 | transparent prevout | 17.51665388 ZEC |
| vin 9 | transparent prevout | 17.53904816 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.