transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
9974ba818238aaa4f2d50ca06b06c3e490147e72ea240849c2025d5d9f77e3b4Public 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 | 1.75593300 ZEC |
| vin 1 | transparent prevout | 1.13000000 ZEC |
| vin 2 | transparent prevout | 1.44588760 ZEC |
| vin 3 | transparent prevout | 2.87450000 ZEC |
| vin 4 | transparent prevout | 0.76512600 ZEC |
| vin 5 | transparent prevout | 1.46792100 ZEC |
| vin 6 | transparent prevout | 1.49747135 ZEC |
| vin 7 | transparent prevout | 0.07178024 ZEC |
| vin 8 | transparent prevout | 1.02953227 ZEC |
| vin 9 | transparent prevout | 7.04060300 ZEC |
| vin 10 | transparent prevout | 0.61929100 ZEC |
| vin 11 | transparent prevout | 1.45288900 ZEC |
| vin 12 | transparent prevout | 1.55563100 ZEC |
| vin 13 | transparent prevout | 1.90027600 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.