A Monero wallet is not one key. It is four: a private spend key, a public spend key, a private view key, and a public view key. Most guides mention this in passing and move on. But if you ever need to prove a payment, let an accountant verify a balance, or set up a watch-only wallet on a machine you do not trust, the view key is the tool that does the job. Knowing exactly what it reveals, and what it never reveals, is the difference between a safe disclosure and a mistake you cannot undo.
What the private view key actually reveals
Monero hides the recipient of every transaction with a one-time address called a stealth address. A public observer looking at the blockchain sees no link between an output and your wallet. Your private view key is what lets software derive those one-time addresses and recognize which outputs on the chain belong to you. Anyone holding your view key can see your incoming transaction history and your total balance, both past and future.
That is the important boundary: the view key exposes receipt, not spending. It cannot move funds, sign anything, or authorize a transfer. Your private spend key does that, and it never leaves your control. There is no scenario where sharing a view key lets someone steal from you.
There is one caveat that surprises people. A view key alone shows incoming funds but cannot prove which outputs have already been spent, because spending is hidden behind ring signatures. To show your true spendable balance, you also share your key images. Key images are derived data, safe to hand over, and they let the verifying software exclude spent outputs. View key plus key images equals a full, auditable picture of an account without exposing the ability to spend.
Four legitimate reasons to share one
Auditing and accounting. If a business or foundation holds Monero, an auditor can import a view key into a watch-only wallet and reconcile every deposit against the books. This is standard practice for organizations that cannot hand a spend key to a third party. The same setup works for shared family funds where one person holds the money and another oversees the records.
Proving a payment was received. In a dispute, a seller can give the buyer’s side or an arbiter the view key for a specific transaction, showing the funds landed. For a single payment, Monero offers something better than the full view key: a per-transaction proof generated by the wallet, which confirms that one transaction without opening your whole history. Use the targeted proof when a full key disclosure is more than the situation needs.
Watch-only monitoring. A view key imported into the official GUI or CLI creates a view-only wallet that tracks incoming payments in real time. Stores use this to detect deposits on a machine that sits in a less secure environment, like a front-desk computer, while the spend key stays on an air-gapped device or hardware wallet.
Backup verification. If you restore a wallet from seed and the balance looks wrong, comparing what a view-only wallet sees helps you determine whether outputs simply have not been scanned yet or something is genuinely off.
How to export it in the official wallet
In the GUI, open Settings, then the Wallet tab, and click “Show keys” or check the box to display private keys. The private view key is the long hexadecimal string labeled as such. Copy it carefully; a single wrong character breaks the import. In the CLI, run viewkey from the wallet prompt while the wallet is open. The command prints both the private view key and, separately, your public keys. Neither command exposes the spend key on screen unless you explicitly request the seed, which you should not do on a shared machine.
To share spend status as well, run export_key_images <filename> in the CLI. Hand the resulting file plus the view key to your auditor. On their side, they create a view-only wallet with your view key and address, then run import_key_images with your file. Their balance display will now match yours exactly.
What you are really giving away, and for how long
A private view key is permanent and irreversible in its disclosure. Once someone has it, they can watch every future incoming transaction to that wallet forever. If that bothers you, the clean answer is wallet hygiene: keep a long-term cold wallet whose view key you never share, and a separate operational wallet for the balances you may need to disclose. Moving funds between your own wallets costs a normal transaction fee and takes the standard 10-confirmation unlock, roughly 20 minutes, before the new outputs are spendable on the receiving side.
Never share a view key belonging to a wallet that also receives funds you would rather keep private, such as personal savings mixed with business receipts. Monero addresses are one-per-wallet by default, and the view key opens the whole address history, not selected parts of it. If you need per-purpose separation, create additional accounts or separate wallets rather than trying to disclose partial history.
Common mistakes
The most frequent error is pasting the spend key when someone asked for the view key. The two strings look identical in format. Always generate them from the same wallet screen, read the label twice, and test the disclosure by importing the key into a fresh watch-only wallet yourself before sending it. If the watch-only wallet cannot see your funds, you exported the wrong thing or the wrong wallet.
The second mistake is sharing a full view key when a transaction proof would have done. For a one-off payment dispute, use the wallet’s transaction proof feature (in the CLI, get_tx_proof). It discloses nothing beyond that single transfer. Reserve proofs, similarly, prove a minimum balance at a point in time without a permanent disclosure. Reach for the full view key only when ongoing visibility is genuinely what the other party needs.
The third is assuming a view key proves you were paid by a specific person. It shows your incoming transactions, not who sent them. If counterparty identity matters, ask the sender for their outgoing proof, or rely on a shared secret like a payment ID or an invoice reference agreed before the transfer.
A sensible disclosure checklist
Before handing over a view key, run through this: confirm the request is for a view key and not a seed or spend key. Decide whether a transaction proof or reserve proof covers the need with less exposure. Import the key into a throwaway watch-only wallet to verify it works and to see exactly what the recipient will see. Send it over an encrypted channel. And if the wallet has future incoming traffic you want private, move to a fresh wallet first and disclose the old one only.
Used with that discipline, the view key is one of Monero’s most practical features: full transparency on your terms, with the spending authority locked away where it belongs.