transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
def098ab24e1a9ac6f1d190215972ac3ef8ac2b2971c02e69293e9b6bec313a5Public 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.17007049 ZEC |
| vin 1 | transparent prevout | 0.19368512 ZEC |
| vin 2 | transparent prevout | 0.20892026 ZEC |
| vin 3 | transparent prevout | 0.22349507 ZEC |
| vin 4 | transparent prevout | 0.24770085 ZEC |
| vin 5 | transparent prevout | 0.24915500 ZEC |
| vin 6 | transparent prevout | 0.26609267 ZEC |
| vin 7 | transparent prevout | 0.44731050 ZEC |
| vin 8 | transparent prevout | 0.92633139 ZEC |
| vin 9 | transparent prevout | 22.40161604 ZEC |
| vin 10 | transparent prevout | 301.70912918 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.