ERPC Improves Historical Transaction Retrieval Centered on Solana RPC getTransaction by up to Approximately 6x — Already Applied Across All Regions and All Solana RPC Plans, Strengthening Data Retrieval for the Latest 30 Epochs
ERPC Improves Historical Transaction Retrieval Centered on Solana RPC getTransaction by up to Approximately 6x — Already Applied Across All Regions and All Solana RPC Plans, Strengthening Data Retrieval for the Latest 30 Epochs
ELSOUL LABO B.V. (Headquarters: Amsterdam, the Netherlands; Representative Director and CEO: Fumitake Kawasaki) and Validators DAO, the operators of ERPC, are pleased to announce a significant performance improvement for historical transaction retrieval centered on Solana RPC getTransaction.
With this update, in our internal comparison environment, getTransaction on ERPC Solana RPC is now up to approximately 6x faster than before the update. The improvement has already been applied across all regions and is available to all ERPC Solana RPC plan users without any additional configuration.
In particular, data retrieval for the latest 30 epochs has been strengthened. As a rough reference, 30 epochs corresponds to approximately two months of recent historical data. This improvement makes it easier to retrieve frequently referenced historical transaction data more quickly for use cases such as explorers, wallets, indexing, analytics infrastructure, monitoring systems, backend APIs, and transaction history checks.
Significantly Improving Historical Transaction Retrieval Centered on getTransaction
Solana applications do not only send transactions. In many production environments, they also need to confirm results, display transaction histories, analyze transaction details, reconcile internal systems, perform monitoring, debug issues, and run indexing pipelines. getTransaction is used in many of these workflows.
Although getTransaction is a basic method for retrieving the details of a single transaction, it is called very frequently in real-world applications. Wallets use it to display transaction histories to users. Explorers and analytics systems use it to inspect the details of each transaction. Trading applications and backend systems also rely on it to confirm the state of submitted transactions and verify what actually happened on-chain.
This update significantly improves the performance of historical transaction retrieval centered on getTransaction. In our internal comparison environment, getTransaction retrieval has become up to approximately 6x faster than before the update. This makes it easier to retrieve more transaction data in less time.
This improvement is not merely about making one method faster. Many Solana applications combine real-time data reception, transaction sending, result confirmation, historical display, analytics, and monitoring. Faster getTransaction responses directly affect the speed of confirmation, display, backfill, and analysis workflows across the application as a whole.
Strengthening Data Retrieval for the Latest 30 Epochs, Approximately Two Months as a Reference
This improvement focuses especially on strengthening data retrieval for the latest 30 epochs. Solana epoch length can vary depending on network conditions, but as a rough reference, the latest 30 epochs correspond to approximately two months of recent historical data.
For many applications, the most frequently referenced data is not extremely old archive data, but recent transaction histories, recent user activity, transactions from the past few days or weeks, events that occurred during active operation, and recent state changes that need to be monitored. By strengthening retrieval performance for the latest 30 epochs, this update focuses on the range that is most likely to be used in real application operations.
Wallets can display recent transaction histories more quickly. Explorers and analytics services can retrieve recent transaction details more efficiently. Indexing infrastructure can more easily perform gap checks, re-fetching, backfilling, and verification. Monitoring systems and backend APIs can benefit from faster incident investigation, transaction confirmation, customer support, and internal reconciliation.
In Solana production environments, slow data retrieval directly becomes operational friction. When transaction details take time to retrieve even after a transaction has completed, user interfaces can lag, internal processes can wait on confirmation, and historical data backfills can take longer than necessary. This update is designed to reduce that friction in historical transaction retrieval.
Already Applied Across All Regions and All ERPC Solana RPC Plans
This getTransaction performance improvement has already been applied across all ERPC regions. It is not limited to a single region, but is active in every region where ERPC Solana RPC is available.
The improvement has also been applied to all ERPC Solana RPC plans. Existing users can benefit from this update without changing plans or adding any configuration. New users who try ERPC Solana RPC can also test the current environment with this improvement already reflected.
ERPC provides Solana RPC, WebSocket, Solana Geyser gRPC, Solana Shredstream, VPS, and bare metal servers on the same platform. By continuously improving Solana-specialized network placement, server configuration, data delivery, and operational tuning, ERPC is building an environment where users can handle more Solana data faster and more reliably.
This update is part of that continuous improvement. ERPC does not only add new features. We also continue improving the performance of existing plans and core methods that are already in use. For both existing and new users, our goal is to make the same plans increasingly useful in real production workloads.
Effective for Explorers, Indexing, Analytics, Monitoring, and Backend Processing
The getTransaction speed improvement is useful across many types of Solana applications.
For explorers and wallets, it makes it easier to display the transaction details that users want to check. Applications in NFT, DeFi, gaming, payments, trading, DePIN, AI x Crypto, and other areas often need to confirm what actually happened on-chain and reflect that result in user interfaces or internal states.
For indexing and analytics infrastructure, Solana events are not only collected in real time. Systems also need to re-fetch transaction details when necessary, verify content, and reconcile results with internal databases. Faster getTransaction retrieval makes these backfill and re-check workflows easier to process efficiently.
For monitoring systems and backend APIs, transaction detail retrieval is also important. To understand what happened for a specific signature, which instructions were executed, which accounts were involved, whether an error occurred, and whether processing matched expectations, getTransaction response speed and stability are important production factors.
In real-time Solana applications, the first arrival of data is important, but so is the entire downstream workflow: confirmation, backfill, recording, display, and analysis. This getTransaction improvement supports those practical post-reception processes.
Expanding Method Coverage, Including DAS-Related Methods
In addition to the getTransaction performance improvement, ERPC has also been expanding supported method coverage. We are continuously broadening support for methods used in real-world operations, including DAS-related methods. For those who previously could not use ERPC because a required method was not supported, we encourage you to test the current support status again.
Solana application requirements vary significantly from project to project. Some projects only need standard Solana RPC methods, while others require combinations involving NFT data, compressed NFTs, asset information, metadata, history, account state, token information, and indexer-style APIs. ERPC continues to expand method availability in response to these practical requirements.
If you previously decided that ERPC did not fit your application because a required method was missing, the current situation may have changed. Please try ERPC again. If a method you need is still unavailable, please create a support ticket in the Validators DAO official Discord. We will review the requirement and use it as a reference for future support expansion.
Free Trial Available for First-Time Users, and Some Previous Trial Users May Be Able to Try Again
If you have not tried ERPC yet, you can use the free trial from the ERPC Dashboard. You can test the getTransaction speed improvement, strengthened retrieval for the latest 30 epochs, and expanded method coverage in an environment close to your actual workload.
Even if you have used a free trial in the past, you may be able to try ERPC again. If you tested ERPC a long time ago and it did not meet your required methods, performance expectations, or application requirements at that time, we encourage you to check the current environment again.
The practical value of Solana RPC depends on method coverage, region availability, response speed, stability, pricing structure, proximity to the application, and operational support. Because ERPC continues to improve, the result today may differ from what you experienced previously. Please test the latest environment and see whether ERPC fits your current requirements.
ERPC Dashboard: https://dashboard.erpc.global/en
Continuing to Improve the Practical Performance of Solana RPC
ERPC treats Solana RPC not merely as endpoint access, but as infrastructure that supports the execution quality of Solana applications. In Solana, network distance, validator quality, server performance, data delivery paths, per-method RPC retrieval performance, and combinations with WebSocket and Geyser gRPC directly affect application experience and operational efficiency.
Even basic methods such as getTransaction are highly important in production. When the performance of core methods improves, developers can handle more data, verify results faster, and build smoother user experiences.
ERPC will continue improving its Solana-specialized infrastructure across Solana RPC, WebSocket, Solana Geyser gRPC, Solana Shredstream, VPS, and bare metal servers. We will continue working on method coverage, retrieval speed, arrival stability, regional expansion, and operational usability so that users can focus on Solana application development and production operations.
Contact
For questions about Solana RPC usage, historical transaction retrieval centered on getTransaction, DAS-related methods, free trials, existing plans, or infrastructure configuration, please create a support ticket in the Validators DAO official Discord.
ERPC Dashboard: https://dashboard.erpc.global/en
ERPC Official Website: https://erpc.global/en
Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR
ERPC Official Website: https://erpc.global/en
Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR
News
