Transaction History


Every transfer you send or receive appears in your transaction history. The list updates as new transfers land on-chain. Tap any entry to open the full receipt on the Tempo block explorer.
Local-first history: Fluxus does not run a history server. The list is rebuilt from on-chain Transfer events plus locally cached entries. Clearing site data resets the cache.
Where to find it
The dashboard at /app shows your most recent transactions in the activity feed below your balance card. The feed combines on-chain Transfer events with locally tracked entries that were just submitted, so a payment appears the moment it confirms.
What you see in each entry
- Direction. A sent or received arrow shows the transfer direction relative to your wallet.
- Counterparty. The other wallet's address, or its registered .pay name when available.
- Amount and token. The transferred value, formatted to 6-decimal TIP-20 precision.
- Memo. The 32-byte transfer note, if present. Memos longer than 32 bytes are truncated at the protocol level.
- Timestamp. The block time of the transfer, shown as relative time in the list.
Filters and search
The activity feed includes a direction filter (All, Sent, Received) and a search field. Search matches against the counterparty address, its .pay name, and the memo text.
Full receipt at /tx/[hash]
Tap any entry to open /tx/[hash], the Fluxus receipt page. The receipt shows the full transaction details, including block number, gas usage, sponsor, and a link to the Tempo block explorer at https://explore.tempo.xyz.
Technical details
- On-chain source. History is built from TIP-20 Transfer events filtered by your wallet address as
fromorto. - Local cache. Locally signed transfers are tracked in a Zustand store (fluxus-tx-history) so they appear instantly. The store reconciles with chain data once events confirm.
- Reverse lookup. Counterparty addresses with registered .pay names display the name instead of the raw hex.
- Privacy. No history data is sent to any Fluxus server. Everything is read directly from the Tempo RPC and your own browser storage.

