transaction
Public facts about this transaction. Zexplorer only shows what the public chain reveals.
4ee3780c70e159415713b12f2f5c041cd9c1f5d9f1e20f822b70818ee5e60429Public counts derived from this transaction's structure. Shielded entries are counted, but their parties, amounts, and memos stay private.
This transaction is a coinbase. It has no spendable transparent inputs; the block-reward output funds the miner directly.
No transparent inputs (coinbase)
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.
Coinbase transactions don't pay a fee: miners receive the block reward instead. The minimum recommended fee below is shown for shape reference only.
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.