transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
4d021a40134f1a0f92fe053464f1f40e493c3267da9e8003c939d4874f85f9cdPublic 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.03837573 ZEC |
| vin 1 | transparent prevout | 0.05570000 ZEC |
| vin 2 | transparent prevout | 0.10013850 ZEC |
| vin 3 | transparent prevout | 0.21920352 ZEC |
| vin 4 | transparent prevout | 0.26416907 ZEC |
| vin 5 | transparent prevout | 0.07833372 ZEC |
| vin 6 | transparent prevout | 0.13269891 ZEC |
| vin 7 | transparent prevout | 0.03840965 ZEC |
| vin 8 | transparent prevout | 69.70258108 ZEC |
| vin 9 | transparent prevout | 0.10516247 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.