Ringdiff

Mainnet privacy report

17 November 2026

How many Solana Privacy Rings transactions leak, and where. Ringdiff reads recent finalized transactions the way a stranger on the chain would, through public RPC with no keys, and labels every field as public, encrypted or unknown. Reports contain counts and public signatures only.

Window
16 Nov 2026, 22:16 UTC to 17 Nov 2026, 10:34 UTC
Slots
470,295,853 to 470,501,861
Read
951 of 1,000 finalized transactions. 49 could not be fetched from the public RPC; 1 could not be decoded.

One dot per transaction

  • 703Transfers with asset and amount encrypted and no recipient in plain view
  • 52Transfers that named the recipient in plain view
  • 178Deposits and withdrawals, where the amount is public as money enters or leaves a ring
  • 18Other Ring activity Ringdiff does not classify yet

Transfers

Amount encrypted
755 of 755 (100.0%)
Asset encrypted
755 of 755 (100.0%)
Recipient public
52 of 755 (6.9%)

A transfer’s recipient is public when the instruction names it inline. Otherwise Ringdiff marks it Unknown, not Encrypted: every output names its signer, so a separate recipient cannot be told apart from change. The sender is always the public signer.

Field visibility by route

RouteCountSenderRecipientAssetAmount
Transfers755755 public52 public703 unknown755 encrypted755 encrypted
Deposits9595 public95 unknown95 public95 public
Withdrawals8383 public83 public83 public83 public
Other Ring instructions1717 unknown17 unknown17 unknown17 unknown
No top-level Ring instruction11 unknown1 unknown1 unknown1 unknown

Check it yourself

Every number above comes from public chain data. Pick any of these transactions and read it the same way:

Terminal
npx ringdiff inspect 3AAAGKUuifbWHcbbZgNBAKeiRcDgGGAvL4kf5NMmr4JdaRFVJLdGB5eny4HfkA5ZrJVE1mZTjbJpTZaCKREt9nU5