Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP XRP Ledger sets a record: 3,254 transactions were packed in one ledger in a single day
On September 14, XRP Ledger (XRPL) packed 3,254 transactions in a single ledger, setting a record high. The record was reached three days after the agreement fix went online.
Key Points
- XRP Ledger verified 3,254 transactions in a single ledger, the highest count in the history of the network.
- Most entries are "one-drop" XRP payments, which Hussein Zangana, community director of the XRPL Foundation, believes may be a throughput test.
- The outbreak follows the fixCleanup3_3_0 patch, which was launched on the main network on September 11 and received support from 31 of the 35 validators.
XRPL transaction record analysis
Hussein Zangana, community director of the XRPL Foundation (online ID: Vet), reported this data after reviewing the ledger. Most entries contain only one "drop", the smallest unit of XRP, equivalent to one millionth of a token. Since his post did not disclose the ledger index and the account information that initiated the outbreak, the identification of this record was mainly based on his personal analysis.
Zangana calls this model a "possible throughput test" and the sender has not yet explained the activity. A ledger that contains only ordinary payments is much less burdensome on the verifier than transactions that contain exchange orders, token operations, or cross-currency paths. Zangana estimates that 500 simple payments may have a lower processing weight than 200 complex transactions.
In addition, the number describes the number of entries that were included in the ledger rather than the number of transfers actually completed, as failed entries still consume fees and remain in the record.
Why XRPL capacity targets are important
Unlike Bitcoin, XRP Ledger does not set a fixed upper limit on the number of transactions within a block. Zangana pointed out that while heavily loaded ledgers can still be closed quickly, the network can increase its soft target value, a result that verifiers regard as a healthy expression of consensus. Conversely, if the shutdown time deviates from the network preference range, the target value may be lowered.
This difference affects the significance of the data: a single crowded ledger does not justify a permanent increase in sustained capacity, which still depends on transaction complexity, hardware performance, and continuous shutdown times. During the outbreak, no operators reported failed consensus rounds, and XRP prices remained around $1.38 during the record spread.
XRPL keeps setting records
This benchmark moves almost every day. On September 13, Zangana counted that ledger No. 106,943,716 contained 2,713 transactions, which was closed in 3.8 seconds; another 2,768 transactions were marked in the following hours. He traced the payments to a network that was triggered collaboratively by 20 accounts and suggested that node operators may need to increase message size limits on connections.
The repair measures behind this operation were launched on the main network on September 11. fixCleanup3_3_0 was activated in verified ledger number 106,911,489 and received support from 31 of 35 validators (support rate of 88.57%).
This patch fixes the treatment of vaults, loans, automated market makers, licensed exchanges, checks and fake accounts. 3.3.0 Five larger features in the software version are still off, with BatchV1_1 closest to activation and supported by 27/35 verifiers, but has not yet reached the two-week 80% support threshold required for the amendment.
