transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
59ab70ecc4a10eb885708afd8a811ae8c298773feb0e71fd8e9c1e67f8d7e634Public 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.54942036 ZEC |
| vin 1 | transparent prevout | 0.54932981 ZEC |
| vin 2 | transparent prevout | 0.91770060 ZEC |
| vin 3 | transparent prevout | 0.54932981 ZEC |
| vin 4 | transparent prevout | 0.91736386 ZEC |
| vin 5 | transparent prevout | 0.91776798 ZEC |
| vin 6 | transparent prevout | 0.54942036 ZEC |
| vin 7 | transparent prevout | 0.55015587 ZEC |
| vin 8 | transparent prevout | 0.91770060 ZEC |
| vin 9 | transparent prevout | 0.73358152 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.