transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
735bc59c219bb72b4eca220f969d7308242e6c8a79e7009fb4c1703ace9626e6Public 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.01343337 ZEC |
| vin 1 | transparent prevout | 0.01310998 ZEC |
| vin 2 | transparent prevout | 0.01207801 ZEC |
| vin 3 | transparent prevout | 0.01266611 ZEC |
| vin 4 | transparent prevout | 0.01174026 ZEC |
| vin 5 | transparent prevout | 0.01281600 ZEC |
| vin 6 | transparent prevout | 0.01200528 ZEC |
| vin 7 | transparent prevout | 0.01214451 ZEC |
| vin 8 | transparent prevout | 0.01287151 ZEC |
| vin 9 | transparent prevout | 0.01229535 ZEC |
| vin 10 | transparent prevout | 0.01202076 ZEC |
| vin 11 | transparent prevout | 0.01198214 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.