Before you accept a Bitcoin payment, paste the sender's address below. HEURISTIC traces its history back toward origin, screens it against the OFAC sanctions list and known entities, and tells you whether an exchange would accept it — with every reason shown.
No need to hunt for a transaction. Open one of these and watch the clustering, coinjoin detection, and taint scoring run live.
10,000 BTC paid for two pizzas in 2010. Trace where the coins came from and watch the change outputs peel off.
69,370 BTC seized by the U.S. DOJ in 2020 — now in government custody. A famous wallet to trace, but receiving from a government auction is clean.
~80,000 BTC moved out of Mt. Gox in March 2011 and sat dormant for years. One of the most-watched wallets on chain.
A major exchange cold wallet. Many-input consolidation sweeps are a textbook common-input-ownership cluster.
374 inputs, dozens of equal-value outputs — the WabiSabi fingerprint our detector keys on, and exactly what breaks clustering.
Looks like an ordinary 2-output payment — but the receiver slipped in an input, quietly defeating the common-input-ownership heuristic.
Part of the 119,756 BTC stolen from Bitfinex in 2016. A textbook flagged origin — watch the acceptance risk light up downstream.
An F2Pool payout address. Its latest transaction sweeps seven mining-payout UTXOs into one — a clean-origin consolidation.
A block's very first transaction — freshly minted coins with nothing behind them. The ⛏ marker means there's no ancestry to trace.
Walk inputs back to their coinbase origin, hop by hop. Every edge is a real spend, weighted by value.
Common-input-ownership union-find collapses co-spent addresses into a single entity — minus coinjoins.
Structural fingerprints for Whirlpool, Wasabi 1 & 2, and JoinMarket — each with a confidence score.
Risk propagates downstream from a seed of documented hacks, seizures, and sanctioned wallets.
By default, queries route through this site to mempool.space — so the operator and mempool.space can see what you look up. Open ⚙ settings and point HEURISTIC at your own electrs/mempool instance: queries then go straight from your browser to your node — nothing touches our servers, no rate limits. Any machine running a full node with electrs/mempool handles it.