// your address
THE SAME INSTRUMENT,
POINTED AT YOU.
Everything on this site is read from one address you have no history with, which means you are being asked to take the reading on trust — the exact position the project this one answers leaves everybody in. So attach a wallet and the identical code runs against an address you do know. Check it against what you remember.
NOTHING IS ATTACHED.
Connecting reveals a public key and nothing else. No signature is requested, no transaction is built — the code to build one is not in this site — and the address is sent to our server only to make the two calls it needs, then dropped.
no wallet has registered with this page. an extension announces itself a moment after load, so reload if one is installed — nothing is listed here rather than a name that would go nowhere
These rows come out of the same four functions the treasury pages use — readBalance, readOutflows, outflowFrom and solOf — imported by this page, not reimplemented for it. A second, tidier version for visitors would prove nothing about the one the treasury figures come from.
- —The amount on each row is your address's own balance change, net of the network fee where you paid it — not a number read off a transfer instruction. A failed transaction moved nothing and does not appear.
- —Only what LEFT is listed. Value arriving is not an outflow, and a page that mixed the two would flatter every address it read.
- —The window is the last 25 transactions, so a busy address shows a sample and the count of what was scanned is printed beside it.
- —No signature was requested and none can be: this site builds no transactions. Connecting revealed a public key, which is a thing anybody can read off the chain anyway.
- —Your address is not stored. There is no database in this project, and the reading is gone when the request ends. One thing IS kept, in your browser and not on our server: the NAME of the wallet you chose — “Phantom”, not an address — so a reload does not pop a dialog at you. Disconnecting deletes it.