transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
197235b59b8e7c71e012ffe898b2c66c5334c725a9a032dfc8bf66f1b1dfbfdcPublic 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 | 16.03757395 ZEC |
| vin 1 | transparent prevout | 21.03718036 ZEC |
| vin 2 | transparent prevout | 24.78584996 ZEC |
| vin 3 | transparent prevout | 20.40294494 ZEC |
| vin 4 | transparent prevout | 16.27724286 ZEC |
| vin 5 | transparent prevout | 19.35329489 ZEC |
| vin 6 | transparent prevout | 15.88380325 ZEC |
| vin 7 | transparent prevout | 24.75484271 ZEC |
| vin 8 | transparent prevout | 16.60940290 ZEC |
| vin 9 | transparent prevout | 20.00000000 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.