Wake
Follow the money.
Wake follows Bitcoin and Ethereum funds forward or back from an address, tells you in percentages where the money went or came from, names the exchanges, mixers and sanctioned addresses on the way, and drafts the request to send to whoever can freeze it.
What Wake gives you
From a single address to a trail you can follow.
Where it went, where it came from
Trace forward or back. A plain-language finding with percentages, an interactive flow diagram, and the addresses that still hold funds. Bitcoin and Ethereum, up to six hops.
Exposure and alerts
Exchanges, mixers, hacks, ransomware and sanctioned addresses are named from public lists, with how far they are from your address and the path to each. Peel chains, splitting and CoinJoin-like transactions are flagged.
Freeze requests
Where funds reached a named exchange or sit in USDT or USDC, Wake drafts the request to send, with the transactions and the report fingerprint.
Reports you can file
A PDF with your case reference, a CSV of the transfers, and a signed JSON. Anyone can check that a saved report was not changed.
Search parameters
Every trace can be narrowed to the question you are asking.
| Parameter | What it does | When to use it |
|---|---|---|
| Direction | Where did it go follows the money forward. Where did it come from follows it back to whoever funded the address. | Forward for theft and fraud. Backward for compliance checks on an incoming payment. |
| Depth | From 1 to 6 transfers away from the address you give. | Start at 3. Go deeper only on the branches that matter. |
| Period | Only transfers between two dates are followed. | Isolate the days of an incident and ignore years of older activity. |
| Minimum transfer | Ignores transfers below an amount, in dollars on Ethereum and in BTC on Bitcoin. | Cut dust, spam and address poisoning. |
| Assets | On Ethereum: ETH only, tokens only, or both. | Follow stablecoins without the noise from other tokens. |
| Detail | How small a share of the money is still worth following: 1%, 0.2% or 0.05%. | Fine for a full picture, broad for a quick overview. |
| Effort | Quick, standard or thorough: how many addresses Wake reads. | Thorough on a serious case, quick for a first look. |
| Excluded addresses | Addresses to ignore. Transfers with them are left out. | Remove your own wallets or a known service address. |
The filters used are printed in the report header and on the PDF, so a reader knows exactly what was and was not followed.
Five views of one trace
Each tab answers a different question.
Overview
The finding in one sentence, the split in percentages, the alerts ranked by severity, and who can stop the money.
Flow of funds
An interactive diagram drawn to scale. Hover to follow one path, click an address for its details.
Addresses and transfers
Every address met, with what it received and sent and why it carries a name, and every transfer grouped by day with a link to its transaction.
Exposure
Sanctioned, hacked, ransomware and mixing addresses met on the way, how far from the start, and the route to each.
Names and alerts
Wake names an address when it can, and says so when it cannot.
| Sanctioned addresses | Addresses published on sanctions lists. Always shown first, with the reminder that the current official listing prevails. |
| Exchanges | Deposit and hot wallets of major exchanges. Tracing stops there, because beyond them lie the exchange’s customers. |
| Mixing services | Mixers and privacy pools. Beyond them, links are guesses, and Wake says so. |
| Hacks and ransomware | Addresses tied to known incidents. |
| Bridges and protocols | Bridges and DeFi contracts, recognised from their verified names. |
| Patterns | Peel chains, splitting across many addresses and CoinJoin-like transactions are flagged. |
Freeze requests
Where the money can be stopped, the request is already written.
For an exchange
When funds reached a named exchange, Wake drafts the message to its compliance team, with the amounts and the transaction hashes.
For a stablecoin issuer
When USDT or USDC still sits at an address, the issuer can freeze it on a valid request. Wake lists the address and the balance.
Sealed to the report
Each request quotes the report fingerprint, so the receiver can check the evidence behind it. You decide whether to send it: Wake never sends anything for you.
The report
A dossier you can hand over, with the raw records at the bottom.
Download a sample report: a real 20-page report, a 2-hop trace of the Ronin bridge exploit (2022), built from public data. The pages above use illustrative values.
How it works
You enter a Bitcoin or Ethereum address, choose whether to follow the money forward or back, and how many hops. Wake reads the public transactions of that address and always follows next the address holding the most money that is still unexplained, so its requests go where the money is. It stops at exchanges, mixers, known contracts and very busy addresses, because following those only leads to their customers. Values are shown in dollars at the price on the day of each transfer.
The data comes from public blockchain explorers. They see the address you trace, not who you are.
Who it is for
Investigators and journalists trace a wallet from a scam or a leak, and hand over a report with the evidence attached. Companies screen an address before accepting a payment: a one-word risk reading first, then the detail, and a PDF for the compliance file. Agencies get a dated, fingerprinted report with its sources and the draft requests to exchanges and issuers.
What you get back
The flags found, where the funds arrived, which addresses still hold money, and the list of transfers with a link to each transaction. Where funds still sit in USDT or USDC, Wake says so: the issuer can freeze them on a valid request.
How accurate it is
Wake shows where funds went, not who owns an address. Links are inferred from public data, and the percentages are an estimate: at each address the money is split in proportion to the transfers that left it. Names come from public lists that are incomplete and can be out of date, and an address with very high activity is only likely to be an exchange. Treat the result as a lead and confirm it before you act. A trace can stop early when the data source limits requests, and it then says so.
Responsible use
Only trace funds you have a lawful reason to follow. Wake must not be used to harass, extort or target a person. The full rules are on the Responsible use page.
Questions
What does a trace cost?
One credit per trace, taken from the credits included in your plan. If the data source fails, the credit is returned.
Which blockchains are covered?
Bitcoin and Ethereum, including tokens such as USDT and USDC on Ethereum. Other chains are not covered yet.
Can I see where the money in a wallet came from?
Yes. Choose “Where did it come from” and Wake traces backward, which is the first step of a compliance check on an incoming payment.
Does it tell me who owns a wallet?
No. It shows where funds went and names known services. It does not identify the person behind an address.
Is my trace stored?
The report is saved to your history, if your plan keeps one, unless you use incognito mode.
How do I keep a report?
Save it as a PDF, export the transfers as a CSV, or download the signed JSON. To check a saved JSON later, use “Verify a saved report” in Wake: it recomputes the fingerprint and tells you if the file was changed.