transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
2c9cd09d99abafb922c54dff9821f9e5f792d445fdd32e0ba397feca5c0956dbPublic 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 | 0.07605451 ZEC |
| vin 1 | transparent prevout | 0.11084372 ZEC |
| vin 2 | transparent prevout | 0.21784945 ZEC |
| vin 3 | transparent prevout | 0.18485775 ZEC |
| vin 4 | transparent prevout | 0.13159575 ZEC |
| vin 5 | transparent prevout | 0.12998700 ZEC |
| vin 6 | transparent prevout | 0.12840300 ZEC |
| vin 7 | transparent prevout | 0.11043449 ZEC |
| vin 8 | transparent prevout | 0.11040975 ZEC |
| vin 9 | transparent prevout | 0.10974146 ZEC |
| vin 10 | transparent prevout | 0.10721699 ZEC |
| vin 11 | transparent prevout | 0.10538547 ZEC |
| vin 12 | transparent prevout | 0.10429648 ZEC |
| vin 13 | transparent prevout | 0.10236584 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.