ERPC Accelerates Solana RPC's getTransaction by up to 6x — Applied Across All Regions and Plans, Enhanced for Latest 30 Epochs
ERPC, operated by ELSOUL LABO B.V. and Validators DAO, announced a significant improvement in Solana RPC's getTransaction performance, now up to 6 times faster. This update is applied across all regions and plans, specifically enhancing data retrieval for the latest 30 epochs, which improves operational efficiency and user experience for various Solana applications like wallets and explorers.
📋 Article Processing Timeline
- 📰 Published: May 9, 2026 at 22:56
- 🔍 Collected: May 9, 2026 at 14:01
- 🤖 AI Analyzed: May 9, 2026 at 14:10 (8 min after Collected)
ELSOUL LABO B.V. (Headquarters: Amsterdam, Netherlands; Representative Director & CEO: Fumitake Kawasaki) and Validators DAO, operating ERPC, are pleased to announce today a significant improvement in the historical transaction retrieval performance, primarily focused on Solana RPC's getTransaction method.
With this update, based on our internal comparisons, ERPC's getTransaction on Solana RPC has been accelerated by up to approximately 6 times compared to before the update. The improvement has already been applied to all regions, and all users of ERPC Solana RPC plans can benefit from it without any additional configuration.
Specifically, data retrieval for the latest 30 epochs has been enhanced. This roughly corresponds to approximately two months of recent historical data. This improvement makes it easier to retrieve historical transactions more quickly within the range frequently referenced in practical operations, such as for Explorers, wallets, indexing, analytics platforms, monitoring systems, backend APIs, and checking transaction histories.
ERPC Dashboard: https://dashboard.erpc.global/ja
ERPC Official Website: https://erpc.global/ja
Significant Improvement in Historical Transaction Retrieval, Centered on getTransaction
In Solana applications, getTransaction is used in many scenarios, not only for sending transactions but also for subsequent result confirmation, history display, detailed analysis, displaying transaction history for users, internal system reconciliation, monitoring, debugging, and indexing.
While getTransaction is a fundamental method for retrieving details of a single transaction, it is called very frequently in practical operations. Wallets use it to display a user's transaction history, and Explorers and analytics platforms use it to check the details of each transaction. It is also an indispensable method for transaction applications and backend systems to confirm the status of sent transactions and to verify what actually happened on-chain.
This update significantly improves the performance of historical transaction retrieval, primarily focused on getTransaction. Our internal comparative verification shows that the retrieval process of getTransaction has been accelerated by up to approximately 6 times compared to before the update. This makes it easier to retrieve more transaction data in a shorter amount of time.
This improvement is not just about one method becoming faster. Many Solana applications operate by combining real-time data reception, transaction submission, result confirmation, history display, analysis, and monitoring. Within this context, a faster response from getTransaction directly relates to the speed of the application's overall confirmation, display, completion, and analysis processes.
Enhanced Data Retrieval for the Latest 30 Epochs, Approximately 2 Months of Data
This improvement specifically enhances data retrieval for the latest 30 epochs. Although the length of a Solana epoch varies depending on network conditions, the latest 30 epochs roughly correspond to approximately two months of recent historical data.
For many applications, the most frequently referenced data is not extremely old archival data, but rather recent transaction history, recent user activity, transactions from a few days to weeks ago, events that occurred during operation, and recent state changes being monitored. By enhancing the retrieval performance for the latest 30 epochs, ERPC is specifically accelerating the range of data most likely to be used in actual application operations.
Wallets can display recent transaction histories more quickly. Explorers and analytics services can retrieve recent transaction details more efficiently. Indexing platforms can more easily proceed with checking for omissions, re-acquiring, supplementing, and verifying data. Monitoring systems and backend APIs can see improvements in the speed of fault investigation, transaction confirmation, user support, and internal reconciliation.
In a production Solana environment, slow data retrieval directly leads to operational friction. Problems such as taking a long time to retrieve details even after a transaction is complete, delays in reflecting data on user screens, waiting for confirmation in internal processes, and slow re-acquisition of historical data affect both application experience and operational efficiency. This improvement aims to reduce this friction in historical transaction retrieval.
With this update, based on our internal comparisons, ERPC's getTransaction on Solana RPC has been accelerated by up to approximately 6 times compared to before the update. The improvement has already been applied to all regions, and all users of ERPC Solana RPC plans can benefit from it without any additional configuration.
Specifically, data retrieval for the latest 30 epochs has been enhanced. This roughly corresponds to approximately two months of recent historical data. This improvement makes it easier to retrieve historical transactions more quickly within the range frequently referenced in practical operations, such as for Explorers, wallets, indexing, analytics platforms, monitoring systems, backend APIs, and checking transaction histories.
ERPC Dashboard: https://dashboard.erpc.global/ja
ERPC Official Website: https://erpc.global/ja
Significant Improvement in Historical Transaction Retrieval, Centered on getTransaction
In Solana applications, getTransaction is used in many scenarios, not only for sending transactions but also for subsequent result confirmation, history display, detailed analysis, displaying transaction history for users, internal system reconciliation, monitoring, debugging, and indexing.
While getTransaction is a fundamental method for retrieving details of a single transaction, it is called very frequently in practical operations. Wallets use it to display a user's transaction history, and Explorers and analytics platforms use it to check the details of each transaction. It is also an indispensable method for transaction applications and backend systems to confirm the status of sent transactions and to verify what actually happened on-chain.
This update significantly improves the performance of historical transaction retrieval, primarily focused on getTransaction. Our internal comparative verification shows that the retrieval process of getTransaction has been accelerated by up to approximately 6 times compared to before the update. This makes it easier to retrieve more transaction data in a shorter amount of time.
This improvement is not just about one method becoming faster. Many Solana applications operate by combining real-time data reception, transaction submission, result confirmation, history display, analysis, and monitoring. Within this context, a faster response from getTransaction directly relates to the speed of the application's overall confirmation, display, completion, and analysis processes.
Enhanced Data Retrieval for the Latest 30 Epochs, Approximately 2 Months of Data
This improvement specifically enhances data retrieval for the latest 30 epochs. Although the length of a Solana epoch varies depending on network conditions, the latest 30 epochs roughly correspond to approximately two months of recent historical data.
For many applications, the most frequently referenced data is not extremely old archival data, but rather recent transaction history, recent user activity, transactions from a few days to weeks ago, events that occurred during operation, and recent state changes being monitored. By enhancing the retrieval performance for the latest 30 epochs, ERPC is specifically accelerating the range of data most likely to be used in actual application operations.
Wallets can display recent transaction histories more quickly. Explorers and analytics services can retrieve recent transaction details more efficiently. Indexing platforms can more easily proceed with checking for omissions, re-acquiring, supplementing, and verifying data. Monitoring systems and backend APIs can see improvements in the speed of fault investigation, transaction confirmation, user support, and internal reconciliation.
In a production Solana environment, slow data retrieval directly leads to operational friction. Problems such as taking a long time to retrieve details even after a transaction is complete, delays in reflecting data on user screens, waiting for confirmation in internal processes, and slow re-acquisition of historical data affect both application experience and operational efficiency. This improvement aims to reduce this friction in historical transaction retrieval.