A token explorer shows a transfer of 25 units to an address. A reader then assumes the address currently owns exactly 25 units. The transfer row alone cannot answer that question. It describes one event, not necessarily the address’s complete history or present balance.
Ask what the interface is displaying
The ERC-20 specification defines a Transfer event with sender, recipient and value fields. It separately defines balanceOf as a method returning an account’s balance. These serve different purposes: one supports an event record, while the other asks the contract for an account value.
For a simple fictional sequence, an address already has 10 units, receives 25 and later sends 8. The incoming transfer row still says 25. Under this simplified example, the resulting balance would be 27. The event was not incorrect; the reader asked it a question it did not answer.
Keep the time context visible
When documenting a discrepancy, record the network, contract, address, transaction identifier and block context. A historical event and a balance query made later can describe different moments. An application may also refresh one part of its display before another.
Do not assume that summing a short visible page of transactions reconstructs an account’s complete balance. Pagination, omitted history and contract-specific behaviour need examination. A convenient activity list is not automatically an accounting ledger with every relevant event.
Read a log without granting it extra authority
An event signature or familiar label does not prove that a contract is trustworthy or fully compliant with a standard. Identify the actual emitting contract and use reliable tooling. Do not connect a wallet or sign a transaction merely to inspect public information that can be read without those actions.
A useful support note says which value you saw, where you saw it and what time or block it represents. “The latest incoming event shows 25, while the balance query at this block returns 27” is a clearer observation than “the explorer is broken.” It gives someone enough context to investigate the difference without treating two distinct interface elements as interchangeable.