Balance is derived, not stored
This is the most important thing to understand about the screen. Your balance is not a counter that gets incremented. It is the sum of your ledger entries — one immutable row per movement, each carrying an amount, akind explaining why, and a reference id pointing at whatever caused it.
The consequence is that you can always ask why a balance is what it is, and get an answer that reconciles. A balance stored as a single number cannot answer that question.
What is on the screen
Reading the transactions list
Each row is one ledger entry. Thekind tells you what caused it:
Amounts are stored as exact decimals, never floats. This matters more than it sounds: commission of 5% on a $29 purchase has to be an exact figure, and
0.05 * 29 in floating point is not one. Rates are held in basis points and amounts in fixed-precision decimals throughout.
Reconciling against the chain
A deposit’s ledger entry references the deposit event, which carries the transaction hash. You can take that hash to a block explorer and confirm independently that what the platform says arrived is what actually arrived.This is the intended workflow, not a power-user trick. The platform is built on the assumption you will verify rather than trust, and every credit is traceable to something on-chain.