ost XRP "whale alerts" show you a single transfer: 50 million XRP moved from an unknown wallet to an exchange. Then the comments start: it must be a sale, it must be a buy, it must be nothing.
A transfer alone cannot answer any of that. What it can't tell you is whether a wallet ended the week with more or less XRP than it started with. That is a different question, and the XRP Ledger can answer it exactly.
The idea: compare balances, not transfers
Instead of counting payments, compare a wallet's balance today with its balance at a fixed point in the past. For example, today's balance against the close of a reference day, in UTC.
This avoids three common traps:
- Round trips. A wallet that sends 100M XRP out and receives 100M back looks busy in an alert feed but has a change of zero.
- Internal moves. Exchanges shuffle XRP between their own wallets all day. Those are not flows. Counting them inflates every number.
- Custody and bridges. A big deposit can be a custody move, not a purchase.
Reading a balance from the ledger
You only need the public API. With the xrpl library:
import { Client } from 'xrpl'; // A full-history public server, so you can also ask about past ledgers. const client = new Client('wss://s2.ripple.com'); await client.connect(); const now = await client.request({ command: 'account_info', account: 'rEXAMPLE...', // any XRP Ledger address ledger_index: 'validated', }); const balanceXrp = Number(now.result.account_data.Balance) / 1e6; // drops → XRP // The same call with a past ledger_index gives the balance back then. await client.disconnect(); Balance is in drops (1 XRP = 1,000,000 drops). For the past value, find the ledger index that closed at your reference time and pass it as ledger_index. The difference between the two numbers is the real change.
Naming wallets without guessing
A balance change is only useful if you know who it belongs to. The rule I follow:
- A name comes from a public source: the known accounts that XRPScan publishes, or an exchange list.
- A name is a public identification, not a guarantee. An exchange can have wallets nobody has identified yet.
- Unnamed wallets stay unnamed. They are shown by address only. Never assign a guessed owner.
Exchange totals then only add wallets that are really on the exchange list. Wallets named after a person, a project or a bridge are shown, but separately.
What the data shows this week
These are the changes between today's balance and the close of November 10, 2026 (UTC), read from the ledger (live table: xrpsonar.com/xrp-whale-accumulation):
- Exchanges combined: −117.4M XRP. Binance −111.2M (now 2.52B), Bithumb −26M, while Robinhood added +38.8M (now 2.41B).
- Ripple's known wallets: −47.4M XRP.
- Whales: 93 increased their balance, 81 reduced it.
- Unnamed wallets: two added +133.1M and +120.6M XRP, and one reduced −212M XRP.
Notice what the table does not say. It doesn't say that someone bought, or that someone sold. A wallet adding balance does not prove a purchase: it may be an internal or custody movement. We only report what the ledger records.
Limits worth stating
- A balance change is not intent. It is the starting point for a question, not the answer.
- Names are incomplete. Some exchange wallets are still unidentified, so exchange totals are a floor, not a ceiling.
- Seven days and thirty days are different stories. A wallet can be up over 30 days and down over 7. Look at both.
Try it
The comparison is published as a free table, updated every 3 hours, in six languages, and the data is licensed CC BY 4.0, so you can reuse it with a link to the source. Each page has a "Cite this data" block with a ready-made source line.
If you build something on top of this, I would like to hear what you would want to measure next.
Data from the XRP Ledger. Not financial advice.
