XRPL Validates 3,254 Transactions in Concentrated Burst

Ledger 106,965,249 closed Sept. 13 at 20:51:50 UTC with 3,254 transactions, including 2,000 one-drop payments from 20 accounts; an XRPL community figure suggested throughput testing.

The XRP Ledger validated 3,254 transactions in ledger 106,965,249 on Sept. 13. The ledger closed at 20:51:50 UTC and included 2,295 successful results and 959 non-success results. Twenty submitting accounts provided 2,000 one-drop XRP payments, with each account submitting exactly 100 payments.

The ledger recorded 2,467 Payment transactions, 458 OfferCreate transactions, 229 TicketCreate transactions, 74 CheckCash transactions, 22 TrustSet transactions, three AccountSet transactions and one NFTokenCancelOffer. Of the 458 OfferCreate transactions, 440 returned non-success codes: 379 tecKILLED and 61 tecUNFUNDED_OFFER. Those 440 failed offers are part of the ledger’s 959 non-success results.

Successful native-XRP Payment transactions delivered 323.641509 XRP. Three successful CheckCash transactions delivered 1,950 XRP, bringing the total across native delivered_amount entries to 2,273.641509 XRP. All Fee fields summed to 111,136 drops, equal to 0.111136 XRP; included fees are destroyed under XRPL fee mechanics.

The XRPL payment model distinguishes direct native XRP transfers from cross-currency and path-based payments that can traverse decentralized exchange offers. Official XRPL documentation states the network uses a soft transaction limit that adjusts with consensus time: the limit can rise when ledgers are fast and fall if consensus takes more than five seconds, and open-ledger costs can increase once thresholds are exceeded.

As of Sept. 15, XRP registered an intraday high of $1.50 and $4.5 billion in 24-hour trading volume. Market indicators noted a Trading Activity score of 84 out of 100 and a Market Signal rated Bullish at 65 out of 100.

An XRPL community figure posting as @Vet_X0 described the ledger as “a new record” and wrote that the submission pattern “probably reflected throughput testing.”

Articles by this author