proof of larp scan a wallet →
field guide / docs

Use the report. Check the receipts.

Start with a public address, then move from the summary to the events underneath it. Every useful number should have a route back to the chain and a note about what it could not establish.

start here

Three steps to a wallet read.

  1. Choose a network and paste an address. Solana is the default. Ethereum addresses are supported through indexed public history.
  2. Read the headline, then the caveats. Realized, unrealized, total, and open positions are different views of the same evidence.
  3. Open an event. Use the explorer link, date, asset, and transaction details to reproduce the important part yourself.
reports & exports

A report you can take with you.

The report view is a portable snapshot: wallet and network, scan time, calculation mode, depth, pricing context, fingerprints, evidence, and limitations travel together. Share links point to the exact snapshot while it is available; they do not create a public account or a permanent identity record.

ReportReadable HTML with the summary, positions, activity, evidence, and caveats.
DataVersioned JSON for machines or a future re-check of the same report.
EventsCSV rows for the classified activity, with native-unit labels and source links.
Browser historyOptional and local to this browser. It is off unless you turn it on.
claims & comparisons

Ask a claim a smaller question.

Claim checks compare a plain-language claim — for example, “this wallet made more than X” — with the report's reconciled evidence. They return supported, contradicted, or indeterminate, plus the specific evidence and limits. A claim is never stronger than the scan beneath it.

Comparison reads two independent public wallets with the same rules. It describes observable activity and scan quality; it does not describe the people behind the addresses.

when a read goes wrong

Failure is information too.

Could not fetchThe provider timed out or refused the read. No invented balance or P&L is shown; retry later.
Incomplete scanSome history, prices, or assets could not be verified. The affected metrics are marked partial.
Unknown basisThe chain does not show a cost basis for the asset, so it stays outside confident P&L.
Unsupported assetThe event remains visible as evidence, but it is not forced into a supported position or quote.
No fallback to fixtures. Test data belongs to development checks only. The configured scanner uses live providers or says it cannot complete the read.
coverage

Supported does not mean everything.

Solana covers token balance changes and common swap evidence. Ethereum covers native ETH and fungible ERC-20 transfers through Blockscout. Ethereum internal transfers, NFTs, and unsupported assets remain outside the current coverage and are disclosed when relevant.