Desk note
Owner, lamports, and the executable flag
People book the desk with an account address more often than they expect. A wallet address and a token account address look similar in a message, and the explorer is where the difference becomes visible. The first field we ask for is the owner, meaning the program that owns the account, not the person who holds a key.
What the owner is telling you
An ordinary wallet is owned by the system program. Its lamport balance is the SOL balance, and the data length is small. A token account is owned by a token program. The parsed view then matters: mint, token owner, and amount. The token owner is the wallet that may spend the tokens. The account owner at the top of the page is still the program. Mixing those two 'owners' is the usual reason a page feels circular.
If the executable flag is set, you are looking at a program account, not a wallet. Data length jumps, and the lamports are there to keep the account rent-exempt, not to spend as pocket money. We do not open source code in a sitting. We do stop long enough to say 'this is a program' so you do not read it as a person.
Lamports before the parsed story
Rent-exempt sounds bureaucratic until an account you expected to close is still on the page with a small lamport remainder. The explorer is showing that the account exists and holds enough lamports for its size. Closing a token account, when the page shows it, is its own instruction and returns those lamports to a named destination. Until you see that instruction, do not narrate the lamports as a fee.
Write three words in the margin before you trust a parsed balance: owner, executable, data length. They take less than a minute, and they prevent the most common misreading we see on account pages in the Jeongeup room.