6 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
Solana has improved its historical data retrieval process by developing a faster and more efficient archival storage system. The new API method, getTransactionsForAddress, significantly reduces the number of RPC calls needed and enhances query flexibility. This overhaul aims to streamline access to transaction data for developers and users alike.
If you do, here's more
Solana has significantly improved its historical data and RPC (Remote Procedure Call) functionality. Previously, querying historical data like transaction details was slow and costly, relying on Google BigTable. Users would often face delays and high costs, needing up to 1,001 RPC calls just to retrieve a handful of transactions. The new system changes this, introducing a distributed archival storage that promises a thousandfold increase in speed and flexibility.
The standout feature is the new API method, `getTransactionsForAddress`, which consolidates multiple calls into one. This method allows users to search for transactions in reverse order and specify time ranges. As a result, calls to get block and transaction details are now ten times faster, reducing latency and the number of required RPC calls dramatically.
Beyond this immediate enhancement, Solana is also working on various features and improvements, including a new client called Frankendancer, ZK compression for lower costs, and improved node requirements with Mythril. These advancements suggest a commitment to making the platform not only faster but also more efficient and user-friendly, addressing common pain points in blockchain data retrieval.
Questions about this article
No questions yet.