transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
32a8b09aac5334ecfac3ca80e08bcf7b9f42057c84dbb54e6a051df95734db7fPublic 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 | 63.92890000 ZEC |
| vin 1 | transparent prevout | 51.21109562 ZEC |
| vin 2 | transparent prevout | 29.39390000 ZEC |
| vin 3 | transparent prevout | 24.82160000 ZEC |
| vin 4 | transparent prevout | 11.69490000 ZEC |
| vin 5 | transparent prevout | 9.93913794 ZEC |
| vin 6 | transparent prevout | 3.64990000 ZEC |
| vin 7 | transparent prevout | 2.97380000 ZEC |
| vin 8 | transparent prevout | 0.99990000 ZEC |
| vin 9 | transparent prevout | 0.49990000 ZEC |
| vin 10 | transparent prevout | 0.06903456 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.