transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
d978b8b961a168333b4f53bcc23040b23c93d917f2efa0d8fee3acf0a205b7d4Public 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.15318575 ZEC |
| vin 1 | transparent prevout | 0.04442950 ZEC |
| vin 2 | transparent prevout | 0.02182601 ZEC |
| vin 3 | transparent prevout | 0.01100000 ZEC |
| vin 4 | transparent prevout | 0.14791120 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.