transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
a4e91014771b220b6d5ba7725744b946ba39a37e9a56e15d7284396ee6b211aaPublic 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 | 369.99990000 ZEC |
| vin 1 | transparent prevout | 199.99899600 ZEC |
| vin 2 | transparent prevout | 547.98693800 ZEC |
| vin 3 | transparent prevout | 35.73437622 ZEC |
| vin 4 | transparent prevout | 199.98990000 ZEC |
| vin 5 | transparent prevout | 39.98990000 ZEC |
| vin 6 | transparent prevout | 33.76176489 ZEC |
| vin 7 | transparent prevout | 49.80974914 ZEC |
| vin 8 | transparent prevout | 2.20275417 ZEC |
| vin 9 | transparent prevout | 92.23487080 ZEC |
| vin 10 | transparent prevout | 2.54991156 ZEC |
| vin 11 | transparent prevout | 0.92240004 ZEC |
| vin 12 | transparent prevout | 99.99899600 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.