Is Monero Traceable? What the Evidence Actually Shows (2026)

"Monero has been cracked" is one of the most repeated headlines in crypto, and it is almost always wrong in the same way: a case that was solved through an exchange, an IP address or a mistake gets reported as a broken blockchain. The honest answer is more useful than either "untraceable" or "cracked", because it tells you exactly where the weak points are.

What Monero hides, and how

Monero uses three separate tools, one for each part of a payment:

These are on for everyone, all the time. That matters: in Bitcoin, privacy tools mark you as unusual. In Monero, every transaction looks the same.

The protections have grown over time. RingCT became mandatory in September 2017, Bulletproofs shrank transactions in October 2018, CLSAG signatures arrived in 2020, and the August 2022 upgrade raised the ring size from 11 to 16 and added Bulletproofs+ and view tags.

What is still visible

Monero is not invisible. Anyone can see that a transaction happened, roughly when, how many inputs and outputs it has, and the fee it paid. A view key, which you can choose to share with an auditor or accountant, reveals incoming payments to one wallet, but not reliably what it spent. These details are small, but they are what statistical analysis works with.

The real cases, one by one

The IRS bounty (2020)

In September 2020 the US tax agency offered up to $625,000 for tools to trace Monero, and later that month awarded contracts worth up to $1.25 million to Chainalysis and Integra FEC. No working on-chain method was ever published from that work.

The 2021 decoy-selection bugs

This one was real and is often left out of "Monero is private" posts. Wallets from version 0.14.1.0 to 0.17.2.2 picked decoys in a slightly wrong way, which in some cases made very recent coins stand out. It was fixed in 0.17.2.3 in 2021. Researchers at TRM Labs later described a related "10-block" pattern and said it was patched in early 2023. The lesson is simple: an old wallet can leak information a new one does not.

The Vastaamo case in Finland (2024)

Investigators in the Vastaamo psychotherapy extortion case said they followed money from Bitcoin, through a no-KYC exchange into Monero, then out through Binance and back to a bank account. They did not say how they linked the Monero part. Because both ends of that trail ran through exchanges, the most likely explanation is the surrounding records rather than the Monero blockchain itself. The suspect, Aleksanteri Kivimäki, was convicted in April 2024.

The spam flood that shrank rings (2024)

Starting on 4 March 2024, the number of small, minimum-fee transactions jumped from around 15,000 to over 100,000 a day. A draft analysis by Monero researcher Rucknium estimated that if one party created them, it owned about three-quarters of recent outputs, which would cut the effective ring size from 16 to roughly 5.5 for transactions made during the flood. The cost to the spammer was estimated at only about 45 XMR. The flood faded by late March. It showed that rings can be diluted cheaply, which is one reason FCMP++ is being built.

The leaked Chainalysis video (2024)

A presentation leaked in September 2024 claimed Chainalysis had traced Monero transactions back to 2021. The method described was running nodes that record the IP addresses of wallets and nodes that connect to them, essentially fake relay points. It is a network attack, not a cryptographic one, and running your own node or using Tor takes most of the bite out of it.

The MAP decoder (2025)

In April 2025 Rucknium's OSPEAD research described a "MAP decoder" that, using statistics about how old real spends tend to be, guesses the real input of a 16-member ring correctly about 24% of the time, compared with 6.25% for a blind guess. That is a meaningful improvement for an analyst and far from a reliable trace, but it is a known, measured weakness of ring signatures.

Spy nodes and malicious remote nodes (2024 to 2025)

A measurement study using data from June 2025 found that 14.38% of observed Monero peers behaved anomalously, consistent with surveillance nodes. Monero responded with a voluntary ban list and, in version 0.18.4.3, with changes that make it harder for many nodes in one network range to surround you. Separately, a wallet bug present from version 0.12.0.0 to 0.18.4.1 leaked the IDs of your outgoing transactions to whichever remote node you used. It was fixed in 0.18.4.2 in August 2025.

The pattern: it is rarely the blockchain

Put the cases side by side and a pattern appears. The traces that worked used one of three things:

• Identity at the edges. Coins bought on a KYC exchange and sent back to a KYC exchange. Monero researchers have warned about this "EAE" setup (the same party sees both ends) since at least 2018.
• Network metadata. IP addresses collected by nodes the user connected to.
• Statistics and old software. Decoy-selection bugs, spam that dilutes rings, and probability models that improve guesses.

What FCMP++ changes

FCMP++ (full-chain membership proofs) replaces the 16-member ring with a proof that your input is one of all eligible outputs on the chain, over 100 million of them. That removes the decoy-selection problem, makes spam flooding pointless and defeats MAP-style guessing. It is the biggest privacy upgrade since RingCT. As of October 2026 it runs on a test network that forked on 5 October 2026, and no mainnet date has been announced.

A practical checklist

1. Update your wallet. Old versions have known leaks. The current official release is 0.18.5.4.
2. Use your own node, or connect over Tor or I2P. Feather does Tor by default.
3. Do not go exchange to exchange. Withdraw to your own wallet and spend from there.
4. Use a new subaddress per counterparty, so different senders cannot see they paid the same wallet.
5. Share view keys sparingly. They reveal your incoming payments to whoever holds them.