How To Read TrackBTC Reports
TrackBTC reports rank on-chain signals by scale, timing, repetition, balance, fees, and address interaction patterns. A high rank means worth inspecting. It does not prove identity, ownership, intent, or off-chain control.
Core Rules
Worked Example: TX 7910fdb3063d...fe2ac944a4
This transaction is useful because it has a very large input, a large same-address change return, and a smaller external movement.
| View | What It Shows | How To Reconcile It |
|---|---|---|
| TrackBTC | Largest External Spend / Transfer: 9,000 BTC from the source address. | The report excludes same-address change and ranks the value that left the address. |
| Mempool tx anatomy | Input value: 139,010.07838347 BTC. Same-address change return: 130,010.07836500 BTC. Fee: 0.00001847 BTC. | 139,010.07838347 - 130,010.07836500 - 0.00001847 = 9,000.00000000 BTC external movement. |
| Reader takeaway | The transaction consumed a very large UTXO position, but the address-level external movement was 9,000 BTC. | Do not read raw input value as economic transfer without checking change. |
Common Misreads
- "Transferred 139K BTC" does not mean 139K BTC of external value moved when most was change return.
- "4.8M lifetime UTXO touches" does not mean 4.8M distinct mempool transactions.
- "2.5M partner-surface links" does not mean 2.5M unique external people.
- "49x displayed median" means relative to this report slice, not all whales globally.
- "31M BTC churn" can happen because the same coins cycle through the wallet repeatedly.
- A balance discrepancy versus a live explorer is not automatically a report error. Check the report block first.
Main Terms
- Input Value
- Total BTC consumed from the sender side of a transaction. It includes value that may return as change.
- Change Return
- BTC returned to the same address in the same transaction. It is not counted as external spend.
- Largest External Spend
- The biggest sender-side amount sent to different addresses in one transaction, excluding same-address change. Same-address outputs are excluded; all non-same-address outputs are included at address level.
- Largest Receive
- The biggest amount received by an address in one transaction.
- Largest External Transfer
- The largest address-level movement where the report can point to a large external spend or receive side. Read it with sender and receiver context.
- Churn Throughput
- External sends plus receives through the address over the window. High churn usually means repeated wallet operations, not accumulation by itself.
- Balance At Block
- The address balance at the exact report height. Use this to separate high churn from retained BTC.
- Address-Side TX Touches
- Window activity count for address participation. It is address-side activity, not lifetime distinct transactions.
- Lifetime UTXO Touches
- Funded UTXOs plus spent UTXOs over the address lifetime. This aligns with mempool-style funded and spent output counts, not mempool distinct tx count.
- Fanout Surface
- Outbound interaction surface. High values can indicate batching, payouts, wallet operations, or broad distribution.
- Fan-in Surface
- Inbound interaction surface. High values can indicate aggregation, deposits, sweeping, exchange intake, or broad receive-side exposure.
- Total Fees Paid
- Ranked by Address fee total: the sender-address share of fees across sender events. Transaction fee total is shown separately for explorer comparison.
- Highest Single Fee
- Ranked by Address fee: the sender-address share of one transaction fee. Transaction fee is shown separately and is the number mempool-style explorers display.
- First Seen / Last Active
- Block heights, not wall-clock times. Use the linked explorer or block height lookup when you need a timestamp.
Cross-Check With Mempool
Mempool is best for raw tx anatomy, current balance checks, distinct transaction counts, and full transaction fees. TrackBTC is best for ranked signals, external movement after change handling, churn, windows, address-attributed fees, and surface-area patterns.
/api/tx/<txid>: inputs, outputs, transaction fee, block height, timestamp
/api/address/<addr>: chain_stats.tx_count is distinct tx count
/api/address/<addr>: funded_txo_count + spent_txo_count maps to lifetime UTXO touches
/api/block-height/<height>: block hash for snapshot anchoring
For current explorer checks, prefer mempool over label or balance aggregator sites. For report claims, compare against the report block height first.
Rough Scale Guide
These are reading aids, not thresholds. Block time is about 10 minutes, so inactive 9 blocks is about 90 minutes and inactive 9,000 blocks is roughly two months. Fee markets move, but a 0.01 BTC single fee is notable, 0.1 BTC is anomalous, and 1 BTC is an extreme single-fee event. Transaction scale below 100 BTC can be routine, 100-1,000 BTC is notable, 1K-10K BTC is large, and above 10K BTC is usually custody, treasury, or exchange-scale movement.
Public Handles
Public pages intentionally truncate address and tx handles. Use the visible explorer links when present. Do not guess the hidden middle of a handle from the preview alone.
Bottom Line
TrackBTC reports are triage tools. They surface where the chain deserves attention. The right next step is inspection, not assumption.