XRPL logs 3,254 transactions in a single ledger close after protocol upgrade
The XRP Ledger recorded 3,254 transactions in one ledger close, according to the XRPL ledger explorer for ledger 106,965,249. The spike came as the network was moving through a protocol upgrade process, but the on-chain data itself does not show why the burst happened or whether it reflected normal user demand.
A technical explanation shared by XRPL validator and XRPLF contributor Vet said the ledger’s higher count fit with the network’s dynamic block-sizing model and adaptive throughput targets. Vet also said most of the transactions were simple 1-drop XRP payments, which suggests the ledger may have been used for throughput testing rather than heavy commercial activity.
What the ledger record shows
The record is notable because it shows the network handling a larger-than-usual transaction set in a single close. But a high transaction count in one ledger does not, by itself, establish a lasting change in XRPL capacity or prove broader usage growth.
Coverage around the event also noted that the ledger arrived while validators were considering features tied to version 3.3.0 of rippled, the network’s reference server software. Those proposed features include BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1 and Sponsor, each of which must still move through the XRPL amendment process before becoming active on mainnet.
In that context, the 3,254-transaction close appears to be a concrete network event, but not a confirmed sign that the protocol has permanently changed its throughput ceiling. No performance report from Ripple, the XRP Ledger Foundation or the reference software maintainers was cited as confirming a lasting capacity increase.
For readers tracking XRPL’s technical rollout, the main detail is narrower: the ledger closed with an unusually high number of transactions, and a network validator said the composition of those transactions points to small-value payments rather than a heavy transaction load.
