QTC Flow Tracer
Follow the money on the quantum chain. Paste any address and walk its transfers hop by hop — or let the pattern radar surface peel chains, distribution fan-outs, consolidation fan-ins and miner forwarding straight from real indexer data. Every edge below is a real on-chain transfer; nothing here is simulated.
🔍 Trace console
Enter a Quantus address (qz…, SS58 prefix 189 — checksum-validated). The console tries the live indexer first (8s), then falls back to the snapshot graph. Tracing is limited to the transfers in the active dataset; see Methodology.
◉ Address dossier
Top senders
Top recipients
☷ Pattern radar
Heuristics run over the full snapshot graph. They flag shapes, not wrongdoing — a peel chain can be an exchange sweeping change; a fan-out can be payroll. Click any row to load it into the trace console.
★ Largest transfers in the dataset
The 25 biggest moves by amount. Genesis block-1 rows are the TGE allocation; everything else is organic chain activity.
| # | Amount | From | To | Block | Time | |
|---|---|---|---|---|---|---|
| loading… | ||||||
ⓘ Methodology & honest limits
- Source. The public Subsquid indexer at
sqm.quantus.com/v1/graphql(transferentity: amount, from/to, block height, timestamp, fee, extrinsic). The browser build tries it live first; GitHub Pages is not on the indexer's CORS allowlist, so the app falls back to the same-origin snapshot. - Snapshot contents. Every transfer ≥ 1 QTC in the 15,000 blocks before capture, plus the 600 largest transfers of all time, plus the full 22-transfer block-1 genesis allocation (merged from the supply-audit snapshot, same indexer). Miner-reward dust (< 1 QTC) is excluded by design.
- Snapshot format. Stored columnar (format v2): addresses and fees are dictionary-encoded and each transfer is one compact row — lossless (every field, including fee and extrinsic id, survives decoding exactly) at roughly half the download of a plain object list. Decoded in-page by the shared
assets/flows-decode.js. - What tracing misses. Transfers below 1 QTC, transfers outside the window, and any move after the snapshot was captured. A trace that ends is a trace that ran out of dataset, not necessarily out of chain.
- Patterns are shapes. Peel chains, fan-outs and fan-ins are structural heuristics. They do not identify owners and do not allege anything about intent.
- Refresh.
node scripts/fetch-flow-data.mjsregeneratesdata/flows.json; commit it to refresh the snapshot.