transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
51b5e29a4b189b4a791b7cfb1bfc9f7381700c9df0ddb3587e7b2881241513ccPublic 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 | 823.98823333 ZEC |
| vin 1 | transparent prevout | 702.37871313 ZEC |
| vin 2 | transparent prevout | 537.31640002 ZEC |
| vin 3 | transparent prevout | 410.36592447 ZEC |
| vin 4 | transparent prevout | 339.64096257 ZEC |
| vin 5 | transparent prevout | 308.25250058 ZEC |
| vin 6 | transparent prevout | 221.38156716 ZEC |
| vin 7 | transparent prevout | 208.20337761 ZEC |
| vin 8 | transparent prevout | 154.01520539 ZEC |
| vin 9 | transparent prevout | 0.00800000 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.