transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
a200a4c23a5c13408dac859118f83fe31218af1c0595b39a5f8b9e61cfa5571dPublic 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.17886965 ZEC |
| vin 1 | transparent prevout | 0.90423081 ZEC |
| vin 2 | transparent prevout | 1.04710688 ZEC |
| vin 3 | transparent prevout | 0.09327383 ZEC |
| vin 4 | transparent prevout | 4.25726705 ZEC |
| vin 5 | transparent prevout | 0.19175003 ZEC |
| vin 6 | transparent prevout | 0.14476235 ZEC |
| vin 7 | transparent prevout | 3.82268075 ZEC |
| vin 8 | transparent prevout | 1.49980000 ZEC |
| vin 9 | transparent prevout | 0.19980000 ZEC |
| vin 10 | transparent prevout | 1.46980000 ZEC |
| vin 11 | transparent prevout | 226.36753742 ZEC |
| vin 12 | transparent prevout | 0.00150876 ZEC |
| vin 13 | transparent prevout | 325.82906627 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.