Starting the application…
The controls will become available when startup succeeds. If this message stays here, JavaScript was blocked or could not start. This is not a wallet or API result.
This is a self-contained static site. Publish this index.html on GitHub Pages; no installation, server process or build step is required.
Local file preview
The application and offline demo work from this file. Live tracing attempts a direct API connection, but the API or browser may reject local-file origins. The intended deployment is GitHub Pages: upload index.html and open the published HTTPS site.
No npm, Node.js, local server or separate backend is needed.
Current balance only. No wallet connection, seed phrase or private key.
Advanced & address labels
No maximum depth or minimum KAS. Browser memory/work safety limits preserve a partial result rather than dropping branches.
API connection
Browser JavaScript cannot tell a CORS block from every DNS/TLS/network failure. The browser console may show the precise reason. This static site uses direct GET requests. If the API blocks your origin, choose a compatible browser-accessible API or retry later. An HTML change cannot grant access on the API’s behalf.
Taking a checked UTXO snapshot…
Amounts are accounted for exactly; source percentages are proportional estimates. A transaction does not uniquely map each input to each output. An exchange is a chosen stopping point, not a source of new KAS.
Discovered endpoints 0
Coinbase evidence, or a public/operator-supplied exchange label.
Unfinished branches 0
Largest remaining contributions first. Nothing here is counted as discovered. Network interruptions keep amounts queued.
Trace paths
Inspect actual transaction outputs, including change and shared ancestry.
| Referenced output / owner | Attributed KAS | State | Action |
|---|
Data quality & limitations
What this trace tells you
1 / Start with what remains
Trace the unspent outputs in a checked snapshot, not a percentage of lifetime receipts. One address is not necessarily an entire wallet.
2 / Follow the funding inputs
Work backwards through specific outpoints. Larger branches get priority, with regular turns for smaller branches.
3 / Stop at evidence
Stop at mining-reward evidence or a labeled exchange. Pause after no new discovery, or press Stop and continue later in this tab.
Methodology, limitations & privacy
For a transaction with mixed inputs, this tracer apportions the target contribution in proportion to input values. Cumulative integer rounding across outputs of the same transaction prevents repeated rounding from exceeding an input. Fees are not added to your balance: the analysis follows only your attributed outputs.
A mining endpoint is supported by an API coinbase flag or the coinbase subnetwork ID. Coinbase payments can include fees. A mining-pool name alone is not evidence of a newly mined payment. Other named entities do not terminate a trace.
Exchange labels identify public/operator-supplied stopping points, not verified beneficial ownership. Unknown exchange addresses may be followed past the exchange and back to mining. Never interpret missing labels, complete model coverage or a long path as proof of the economic origin of funds.
Snapshots are amount/count cross-checked, not block-pinned or cryptographically verified. Indexer errors, missing historical data, reorganizations and public API limits can prevent completion. There is no promise of finding every exchange.
API interruptions suspend traversal and test the failed transaction up to three times per run before pausing. Network failures never mark the whole frontier unavailable. Stop aborts requests; Continue preserves the same snapshot and retries unfinished branches. This in-memory session does not survive reloading the page. Exported JSON is an audit report, not an importable checkpoint. Start a new trace for a fresh balance.
No signing, tracking analytics or third-party scripts are used. The selected API can see queried addresses and transaction IDs. The API receives your IP address. This application uses no relay, wallet connection or backend, and it does not silently switch providers. Exports contain public-address tracing history; share them deliberately.
Empty addresses have no current balance to trace. Lifetime-receipt tracing from v1 has intentionally been removed rather than mixed with current-balance attribution.