Methodology
What the tools actually do, the heuristics behind the Brief, and where the limits are. Stated plainly, because the whole point is to be verifiable rather than authoritative.
Radar
The radar polls mempool.space/api/mempool/recent roughly every 25 seconds and keeps only
transactions at or above the chosen threshold (50, 100, 500, or 1000 BTC). It also fetches the BTC/USD
price from CoinGecko for the approximate dollar column. Everything is computed in your browser; nothing is stored.
The public /mempool/recent endpoint returns only the most recent handful of pending transactions —
not the whole mempool. Large transactions arrive in bursts, so the view can be sparse between arrivals. This is
the live tip, not a historical feed.
Brief
Given a transaction id, we fetch mempool.space/api/tx/{txid} and apply simple structural heuristics:
- One input → many outputs suggests a distribution or batch send.
- Many inputs → one output suggests a consolidation.
- One in → one out is treated as a simple transfer.
- Any output (or input) matching our public label list flags a labeled movement.
The summary carries an explicit certainty qualifier — probably, possibly, or high uncertainty — and the decision logic is shown step by step so you can audit it.
Labels
The directory is exact-address-match against a manually curated list. Each entry records a category, a confidence level, and a public source. It is intentionally small and conservative. We do not cluster addresses or infer ownership.
Limits, honestly
- Real ownership and intent are not knowable from public chain data alone.
- Address reuse and exchange internals mean labels can be stale or partial.
- The dollar values are approximate and depend on a live price feed that can fail.
- None of this is financial advice.
Sources
mempool.space REST API, CoinGecko simple price, and the per-entry sources cited in the label directory. Code is open on GitHub.