understanding the data behind wen withdraw
The anonymity set is the number of deposits of the same amount as your withdrawal. Higher is better.
If 500 people have deposited 0.1 ETH and you withdraw 0.1 ETH, your withdrawal could plausibly be any of those 500 people. That's your anonymity set.
A unique amount like 1.337 ETH might have an anonymity set of 1. That means if you withdraw it, there's only one possible depositor: you.
The "suggested wait time" shows the average interval between deposits of the same amount.
This tells you: if you want to withdraw 0.1 ETH and blend in with the crowd, a new deposit of that amount happens roughly every 18.5 hours on average.
A deposit is "unclaimed" when the total number of deposits of that amount exceeds the total number of withdrawals of the same amount.
Withdrawals only. Ragequits (v2) are counted and displayed separately because they exit notes the ASP never approved, and those notes were never part of the deposit count. Subtracting them would double-count the exclusion.
This is a heuristic, not a guarantee. Privacy Pools is designed so you can't actually know which deposit corresponds to which withdrawal. That's the whole point.
The unclaimed count just tells you: more people have deposited this amount than withdrawn it. There's room in the pool for your withdrawal.
You already have funds deposited in the pool. You search for an amount like "0.576" and see it has 1 deposit and 0 withdrawals. That deposit is unclaimed. If you withdraw 0.576, your withdrawal matches that specific deposit.
Deposits go through a review process before being accepted into the ASP (Association Set Provider). Pending deposits are not yet in the pool.
You cannot withdraw against a pending deposit. Wait for it to be approved first. The tool excludes pending deposits from timing recommendations and unclaimed calculations.
All data comes from the 0xbow public API at api.0xbow.io. The tool fetches deposit and withdrawal events, caches them in your browser for 15 minutes, and lets you filter by token, chain, and time period.
No data is sent anywhere. Everything runs in your browser.
Privacy Pools v2 adds two event types that the scores treat differently from deposits and withdrawals.
A transfer moves value between notes inside the pool. The note is consumed and re-minted at a new amount; nothing leaves the pool and no address appears onchain. A transfer of 0.5 ETH means someone now holds a live 0.5 ETH note, so that note is a plausible source for a 0.5 ETH withdrawal.
Transfers of an amount count toward SET SIZE, RECENCY, and FREQUENCY alongside deposits. They never count as withdrawals.
A ragequit is the public exit of a note the ASP never approved. Since pending and declined deposits are already excluded from the deposit side of the math, the note a ragequit exits was never counted. Ragequits get a RAGEQUIT badge and a per-amount count, but they never reduce UNCLAIMED.
Opsec tip (v2 only): if your deposit amount is unique, do an internal transfer to a fresh amount before withdrawing. The transfer re-denominates your note, so your withdrawal no longer matches your deposit amount and the direct deposit-to-withdrawal link is broken.
The Anon Score is a 0–100 composite score that measures how safe it is to withdraw a given amount right now. It's used to rank amounts on the "wen withdraw?" leaderboard.
| Score | Label | Meaning |
|---|---|---|
| 80–100 | EXCELLENT | Strong anonymity, safe to withdraw |
| 60–79 | GOOD | Reasonable cover, low risk |
| 40–59 | MODERATE | Some risk, consider waiting |
| 20–39 | POOR | Limited cover, you may stand out |
| 0–19 | RISKY | Very little anonymity, wait for more deposits |
The leaderboard on the "wen withdraw?" tab ranks all deposit amounts by Anon Score so you can quickly find the safest amount to withdraw.
Instead of "how safe am I?", it asks "how easy is it to identify me?" Enter your deposit time and the tool calculates a Detection Risk %. This is the probability an analyst could link your withdrawal back to your deposit.
The chart shows detection risk across time buckets (0–1h, 1–6h, 6–24h, 1–3d, 3–7d, 7d+). Risk decays roughly exponentially, the first few hours carry the most danger.
>60% HIGH Analyst can likely identify you.
30–60% MODERATE Grey area. More cover would help.
<30% LOW You blend in with enough other depositors.
Enter when you deposited to unlock the attacker view and personalized timing analysis.
Paste a full transaction hash (e.g. 0xabc123...) and the tool will look up its timestamp from the loaded deposit data. If your tx hash matches a known deposit, the time is extracted automatically.
When a pasted tx hash matches a deposit in the loaded data, the tool also auto-fills the amount, token, and chain dropdowns. This saves you from entering those fields manually and avoids mismatches.
If the tx hash isn't found in the loaded deposit data, the tool falls back to public RPCs for supported chains (Ethereum, Arbitrum, Optimism) to look up the transaction timestamp. This is slower but lets you use any valid deposit hash.
The heatmap shows when deposits happen by day of week and hour (UTC). When v2 data is in view it also counts internal transfers, which re-mint notes at the same amounts. Darker cells mean more activity.
Use this to withdraw when others are active. Blend in with the crowd. Avoid withdrawing at 3am on Tuesday if no one else does.
If your deposit amount has a small anonymity set, the tool suggests splitting your withdrawal into multiple smaller amounts that each have better cover.
It finds denominations with high anonymity sets that add up to your target. Each piece is scored individually. Withdraw the pieces at different times - withdrawing them all at once from the same wallet defeats the purpose.
This tool cannot tell you definitively which deposit your withdrawal will be linked to. Privacy Pools uses zero-knowledge proofs specifically to prevent that.
This tool gives you data to make better opsec decisions. It's not a guarantee of privacy.
privacy is normal