transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
8e90112162275dcdbf341afa790ed21edbc7edfb55b843599ac33d61b5c3239bPublic 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 | 5.16198185 ZEC |
| vin 1 | transparent prevout | 1.76679051 ZEC |
| vin 2 | transparent prevout | 0.50919569 ZEC |
| vin 3 | transparent prevout | 0.49448900 ZEC |
| vin 4 | transparent prevout | 0.38406800 ZEC |
| vin 5 | transparent prevout | 0.24170000 ZEC |
| vin 6 | transparent prevout | 0.17553360 ZEC |
| vin 7 | transparent prevout | 0.11102748 ZEC |
| vin 8 | transparent prevout | 0.11074778 ZEC |
| vin 9 | transparent prevout | 0.10177080 ZEC |
| vin 10 | transparent prevout | 0.03631126 ZEC |
| vin 11 | transparent prevout | 0.01891503 ZEC |
| vin 12 | transparent prevout | 0.01212095 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.