transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
e8fdbe84f2b1fed7280f8ee2a082891d28400273589a2914b5b7eb72ba9b9505Public 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.71454023 ZEC |
| vin 1 | transparent prevout | 11.53849971 ZEC |
| vin 2 | transparent prevout | 14.72460671 ZEC |
| vin 3 | transparent prevout | 16.74434875 ZEC |
| vin 4 | transparent prevout | 25.85000444 ZEC |
| vin 5 | transparent prevout | 28.27189899 ZEC |
| vin 6 | transparent prevout | 30.64624891 ZEC |
| vin 7 | transparent prevout | 11.98690682 ZEC |
| vin 8 | transparent prevout | 12.18999056 ZEC |
| vin 9 | transparent prevout | 11.56188389 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.