Following the money onchain with GoldRush Fund Flow Tracer
Fund Flow Tracer follows crypto across chains, swaps, lending pools and bridges, and turns the result into evidence exchanges and issuers can act on.
After a hack, a scam or a drained wallet, everyone asks the same question: where did the money go? Answering it by hand means hours in block explorers, a spreadsheet of transaction hashes, and guesswork about which transfer out of a busy wallet carried the stolen funds.
Fund Flow Tracer answers that question with GoldRush data. Give it an address, a transaction hash or an ENS name, and it follows the funds across chains and through swaps, lending pools and bridges to where they sit today. Then it packages what it found as evidence that an exchange, a stablecoin issuer or the police can act on.
Fund Flow Tracer is part of the GoldRush platform. A trace runs on a GoldRush API key from your own account, so every figure in a case comes straight from a GoldRush API response.
Starting a trace
Fund Flow Tracer opens with one question: What happened? Either funds were lost or stolen, or you want to check an address before sending money to it.
Paste a transaction hash and the trace starts right away. Paste an address and Fund Flow Tracer lists its transfers so you can pick the ones that were lost. Trace many combines a list of addresses, transactions or ENS names, pasted or imported from a CSV, into one case.
By default a trace follows the funds 2 hops and spends at most 10,000 GoldRush credits. You can raise these to 6 hops and 25,000 credits, or choose Complete to run until everything is followed. A trace only uses the credits its calls need.
Following the funds
The trace keeps going where funds are commonly moved to hide them:
Swaps. Swapped tokens are followed as the new token, at the swap's rate. Funds added to a liquidity pool are followed through the liquidity tokens or position. A check stops a long run of swaps from adding up to more than was stolen.
Lending. Deposits into Aave, Spark and Compound are followed, and so is any money borrowed against them. Borrowed money is shown separately and never added to the stolen total.
Noise. Tiny amounts, spam tokens and lookalike addresses are ignored. When funds split across more than 8 wallets, the trace follows the 8 largest and groups the rest.
A trace ends where the money lands: an exchange, a mixer or a burn address. A sanctioned address is flagged, and the trace keeps going.
Across chains
Fund Flow Tracer works on EVM chains and Bitcoin. It follows funds to another chain wherever the destination is recorded onchain: Across, the Arbitrum and OP Stack bridges, Circle's CCTP, LayerZero, Wormhole, deBridge, Allbridge, Relay, Umbra and LI.FI. THORChain swaps are followed to where they were paid out, including to Bitcoin, and USDC bridged into Hyperliquid is followed on the Hyperliquid account.
Mixers are built to break the trail. When funds enter Tornado Cash, Railgun or Privacy Pools, Fund Flow Tracer lists up to 5 withdrawals that might be the same money, each with its reasoning, as low-confidence suggestions rather than findings. If you follow one, everything after it is marked "Chosen by the reader, unconfirmed" and isn't counted in the case's totals.
Where the funds ended up
Each trail ends with a plain status, such as still in a wallet, sent to an exchange, bridged, mixed, swapped and spread out, or deposited in a lending pool. When $10,000 or more of a freezable token such as USDT or USDC is still in a wallet, Fund Flow Tracer asks the token's contract whether the issuer has frozen it.
Wallets are named from a built-in set of about 3,700 labels, drawn from protocol documentation, Binance's and Bybit's own proof-of-reserves lists, and the US Treasury's OFAC sanctions list. Each label records its source, retrieval date and confidence. Fund Flow Tracer says plainly that labels are informed judgements, not verdicts.
Evidence others can act on
A case can be exported as:
Freeze requests for each exchange and stablecoin issuer (Tether, Circle) involved, with deposit addresses, transaction hashes, times, exact amounts, the path from the start and, where published, the exchange's law-enforcement contact page.
A CSV of every transfer for legal requests, with recorded facts kept apart from inferences.
A method sheet in every export, stating each assumption the case relied on. It ends with a SHA-256 fingerprint of the case file, so a recipient can confirm it hasn't been altered.
Fund Flow Tracer reports what happened. It doesn't give advice or promise that funds can be recovered.
Working on a case
Each case has a Graph of the flow and Paths between any two wallets. On your own cases you can edit the Graph; anything you add is marked "Added by the reader" and never counted in the totals.
Sharing a trace
Once a trace has found transfers, you can share it. Share publishes a read-only copy of the case at its own link. Anyone with the link can open it without signing in and see the same views you do: where the funds are now, every transfer, the Graph and the paths. The link comes with a preview card showing the amount traced and where it went, and it isn't indexed by search engines. Your private notes stay out unless you choose to include them, and Stop sharing takes the link down.
Checking an address before you send
The other option on the first screen checks an address before you pay it: its labels, whether it's sanctioned, and how much of its money came from or went to sanctioned, darknet, exploiter, scam or mixer addresses, within 3 hops. A check costs 40 credits by default and never more than 100.
Tested on real hacks
Fund Flow Tracer comes with twelve worked examples from well-known hacks, including Binance, Bybit, Ronin, Euler and Wintermute.
The Binance hack, traced
On 29 October 2026, Binance's hot wallets were drained. TRM Labs puts the loss at about $6.3 billion, the largest hack on record, and attributes it to North Korea. In the first half hour alone, $4.95 billion left Binance across seven chains. Most of it went to one wallet, now labelled Binance Hot Wallet Exploiter 2: $1.82 billion in USDT and 169,534 ETH from the wallet labelled Binance 14, then $823 million in USDC from another Binance hot wallet.
Fund Flow Tracer followed 6,951 transfers from there and accounts for $5.31 billion. Here is what it found.
$2.34 billion is frozen. Fund Flow Tracer asked each token's own contract whether the funds in the hacker's wallets were frozen. $2.31 billion of it was:
$1.38 billion in USDT, frozen by Tether.
$825 million in USDC, frozen by Circle.
About $58 million in tokenised gold: 12,574 ounces in XAUt and 1,907 ounces in PAXG.
Smaller amounts in USD1, FDUSD, USDP, and USDT on Polygon and Avalanche.
A further $31 million, 8,426 ETH and 74.6 million ARB, ended up in a wallet held by Arbitrum's governance.
Some tokens were burned out from under the hacker. $4.2 million in tokens such as BEAM was burned from the hacker's wallets in transactions the hacker didn't send, most likely by the tokens' issuers.
The hacker sold and borrowed. 146 different tokens, from PEPE to LINK, were swapped into ETH more than 3,000 times, the largest 325 million USDT for 122,316 ETH. 60 million stolen USDT went into Aave as collateral for a 19,762 ETH loan, and $24.3 million of that collateral was later seized in a liquidation; $35.5 million is still in Aave. Fund Flow Tracer followed the borrowed ETH too, but never counted it as stolen.
Some of it went back to Binance. $5.5 million in tokens such as SAND and SNX reached a Binance reserves wallet.
The Bitcoin hasn't moved. All 18,270 BTC, about $1.49 billion, still sits in the 19 wallets it was first sent to. With the rest of the unfrozen funds, $2.75 billion in all, those are the addresses to watch.
That's the case as Fund Flow Tracer shows it. It's one of its worked examples, so you can open it and explore it yourself without spending a credit.
See the Binance case in Fund Flow Tracer: goldrush.dev/trace/example/binance-14