transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
4e5e7f92c21ff39896aa7562c1215145ab7e4043af2460aaec3b3fae7dd86badPublic 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 | 29.91369997 ZEC |
| vin 1 | transparent prevout | 32.90099847 ZEC |
| vin 2 | transparent prevout | 52.49704883 ZEC |
| vin 3 | transparent prevout | 1957.00000000 ZEC |
| vin 4 | transparent prevout | 3500.00000000 ZEC |
| vin 5 | transparent prevout | 30.38184233 ZEC |
| vin 6 | transparent prevout | 32.80421274 ZEC |
| vin 7 | transparent prevout | 47.07670758 ZEC |
| vin 8 | transparent prevout | 47.64342117 ZEC |
| vin 9 | transparent prevout | 45.41656801 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.