TLDR
- The XRP Ledger processed 3,254 transactions in one ledger, setting a new reported record for single-ledger activity.
- Most transactions were one-drop XRP payments, suggesting the spike may have come from throughput testing rather than normal user activity.
- The record does not mean XRPL permanently raised its transaction limit, because the network uses an adaptive transaction target.
- Simple XRP payments place less load on the network than more complex transactions, making transaction type important when judging capacity.
- The record comes as XRPL prepares several upgrades from xrpld 3.3.0, including BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, and Sponsor.
The XRP Ledger has recorded its largest known transaction count within a single ledger, according to XRPL validator Vet. One ledger processed 3,254 transactions, setting a new reported record for the network.
The activity mainly involved very small XRP payments. Vet said most transfers moved only one drop, the smallest unit of XRP, and suggested the activity could represent throughput testing.
XRP Ledger Record Driven by Small Payments
The transaction count does not mean the XRP Ledger permanently raised its processing limit. The network does not use one fixed maximum number of transactions for every ledger. Instead, its transaction target can adjust based on network performance.
Vet explained that validators can handle more transactions when a ledger closes quickly despite carrying activity above its current target. This system allows the network to respond to processing conditions rather than follow one fixed transaction count.
3254 transactions in a single block a few hours ago on the XRP Ledger. New record.
Good opportunity to review an interesting characteristic of the XRP Ledger vs Bitcoin.
Our blocks are dynamic in size limits and not fixed like Bitcoin. XRPL transaction capacity is an adaptive…
— Vet (@Vet_X0) September 14, 2026
The record also requires context because transactions can place different demands on the network. The 3,254 transactions mainly consisted of simple payments, which require fewer resources than more complex operations carried out through the ledger.
As a result, 3,254 basic XRP payments do not represent the same workload as an equal number of complex transactions. Vet said transaction types differ in their load footprint, making the nature of activity important when assessing network capacity.
XRPL Prepares New Protocol Upgrades
The record arrives as XRPL developers prepare several protocol changes introduced through xrpld version 3.3.0. Developers released the software on August 6 with new amendments and a group of protocol fixes for XRP Ledger servers.
The release introduced BatchV1_1, ConfidentialTransfer, DynamicMPT, PermissionDelegationV1_1, and Sponsor. BatchV1_1 allows accounts to bundle multiple transactions, while other amendments add features covering token transfers, account permissions, sponsorship, and Multi-Purpose Token functions.
Under BatchV1_1, an account can submit up to eight inner transactions in one batch. ConfidentialTransfer adds private transfers for certain tokens, while Sponsor lets another account cover transaction fees or reserve costs under defined conditions set by the protocol.
BatchV1_1 was closest to reaching the required validator support level on September 14. Vet reported that 27 of 35 trusted validators were signaling support for the amendment at that time.
The record ledger and pending amendments remain separate developments. The 3,254-transaction ledger shows how the network handled a large group of simple payments, while validator voting determines whether proposed protocol features become active on the XRP Ledger.
