A wallet interface shows a balance, but the person viewing it cannot sign a transaction. A watch-only setup can monitor public wallet information without holding the private keys needed to authorise spending.
Bitcoin Core’s documented import behaviour provides a clear example: importing an address or script without all required private keys can result in watch-only status. That page documents an older software version, so it is cited for the concept, not as a current setup tutorial.
Separate observation from control
Public transaction information can show activity associated with an address. It does not establish that the person displaying it owns the funds or can move them. A screenshot of a large balance is therefore weak evidence for a claim of wealth or access.
Legitimate watch-only arrangements can be useful for monitoring while signing remains on separate equipment. The exact workflow depends on the wallet, network and signing arrangement. Use current official documentation for the tools involved.
Keep public information private when appropriate
Public does not mean harmless to share. Revealing an address or extended public information can connect transactions to a person or business. Consider what a viewer could learn before sending wallet details to a stranger or posting them publicly.
Never provide a seed phrase or private key merely to make a watch-only display work for someone else. Treat demands for an activation payment to unlock a displayed balance with scepticism, and verify the situation independently through trusted channels.
If testing your own setup, confirm what information was imported and where signing authority actually resides. A displayed balance, a transaction draft and a valid signature are different stages.
The practical question is not only “Can I see the funds?” It is “Which device or authorised party can sign, and how do I verify that safely?” Keeping those roles distinct makes wallet interfaces less misleading.