transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
00f9fcb8f4c22969967809ef7372d9e598484bdfa4c1c2ffe86d042fd0b8a737Public 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.88737927 ZEC |
| vin 1 | transparent prevout | 0.89986000 ZEC |
| vin 2 | transparent prevout | 0.89986000 ZEC |
| vin 3 | transparent prevout | 0.89990000 ZEC |
| vin 4 | transparent prevout | 0.91015272 ZEC |
| vin 5 | transparent prevout | 0.91990000 ZEC |
| vin 6 | transparent prevout | 0.92946961 ZEC |
| vin 7 | transparent prevout | 0.96719339 ZEC |
| vin 8 | transparent prevout | 0.97990000 ZEC |
| vin 9 | transparent prevout | 0.98004315 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.