XRPL Hit 3,254 Transactions in One Ledger — All From 20 Accounts

A Record Count With an Asterisk

On September 13, the XRP Ledger closed ledger 106,965,249 at 20:51:50 UTC containing 3,254 transactions – a figure that XRPL community member @Vet_X0 immediately flagged as a new record for the network. The ledger included 2,000 one-drop XRP payments, each worth a fraction of a cent, submitted by exactly 20 accounts sending exactly 100 payments apiece. The geometric precision of that distribution points to deliberate throughput testing rather than organic user activity.

The result demonstrates that XRPL consensus can process and finalize an unusually large transaction set in a single ledger close. What it does not demonstrate is how the network would behave under equivalent pressure from thousands of independent participants, varied transaction types, and real economic stakes spread across the order book.

Breaking Down the 3,254 Transactions

Of the 3,254 included transactions, 2,295 finished with successful results and 959 did not. The 2,000 one-drop payments accounted for the bulk of the successful group. The full transaction composition also included 2,467 Payment transactions total, 458 OfferCreate transactions, 229 TicketCreate transactions, 74 CheckCash transactions, 22 TrustSet transactions, three AccountSet transactions, and one NFTokenCancelOffer – a deliberate mix designed to stress different parts of the ledger’s processing logic simultaneously.

The failure rate within OfferCreate activity stands out. Of 458 OfferCreate transactions, 440 returned non-success codes: 379 coded as tecKILLED and 61 as tecUNFUNDED_OFFER. Those 440 failed offers represent the majority of the ledger’s 959 non-success results. XRPL’s fee mechanism still destroys the fee attached to transactions that close with certain failure codes, which means failed activity has a direct, measurable effect on XRP supply regardless of whether the underlying operation succeeded.

On the value side, successful native-XRP Payment transactions delivered 323.641509 XRP across the ledger. Three successful CheckCash transactions added another 1,950 XRP, bringing the total across native delivered_amount entries to 2,273.641509 XRP. All Fee fields across the full 3,254 transactions summed to 111,136 drops – equal to 0.111136 XRP destroyed permanently. The broader ledger also carried issued-currency activity through its OfferCreate and cross-currency payment mechanics, but those values cannot be added to the XRP figures directly because the two asset types use different units and different settlement logic.

What the Capacity Signal Actually Measures

XRPL’s transaction throughput is not a fixed ceiling. The network’s soft transaction limit rises automatically when a ledger exceeds it, and falls back when consensus takes more than five seconds to close – at which point the open-ledger cost can increase exponentially. Ledger 106,965,249 cleared inside normal closing parameters, but the 20-account, uniform-submission structure kept the workload concentrated in a way that real-world usage rarely replicates.

The XRPL Payment reference draws a clear distinction between direct XRP transfers and cross-currency or path-based payments. Cross-currency transactions route through intermediary steps and consume decentralized exchange offers along the way, creating a significantly heavier processing load per transaction. A ledger built primarily around 2,000 micro-payments from 20 coordinated accounts does not approximate that complexity, which makes raw transaction count a limited basis for assessing what the network can handle at scale.

XRP Market Conditions on September 15

Two days after the ledger closed, XRP was trading with an intraday high of $1.50 and registered $4.5 billion in 24-hour trading volume as of September 15. The asset’s Trading Activity indicator sat at 84 out of 100, and its Market Signal read Bullish at 65 out of 100. Whether the throughput test influenced any of those figures is not something the on-chain data can answer – market sentiment and ledger stress tests operate on different timescales with different audiences.

For those watching the XRP Ledger’s technical development, the September 13 ledger offers two concrete data points: 2,273.641509 XRP moved through successful native payment activity, and 0.111136 XRP was permanently removed from supply through transaction fees. The coordination required to produce 2,000 identical micro-payments from 20 accounts also suggests an organized effort to probe the ledger’s limits under controlled conditions rather than under market pressure.

The stablecoin layer on XRPL adds further context to why capacity testing matters right now. Circle recently minted 10 billion ARC tokens with BlackRock and Visa joining as validators, signaling institutional appetite for ledger throughput that looks very different from 20 accounts running coordinated payment batches.

The 440 failed OfferCreate transactions – each still paying a fee, each still counted toward the ledger’s non-success total – sit at the center of the capacity question nobody has answered yet: what happens to XRPL’s fee dynamics and consensus timing when that volume comes from parties who actually need the trades to clear?