The goal of eosq, the high-precision block explorer built by the EOS Canada team, is to help developers find the key information they require from the blockchain. One of the main feats we first set out to tackle was the data pipeline on which eosq would rely, which was the genesis of the dfuse API for EOS.
A Unique Backend
Shortly, we identified that relying on the nodeos history API was not a feasible option for an EOS block explorer due to its oversimplified data architecture, which was never designed with long-term big data scalability in mind.
As of recent, fewer teams have been able to provide an API endpoint with full history as it is becoming too expensive to provision a server with enough RAM and service the requests. We have instead been focusing with dfuse on building out a robust big data architecture.
Developers of dapps who want to learn more about the first streaming API solution for blockchain can apply for a free API key to see the strength of dfuse.
The level of detail that eosq offers when exploring a transaction is unmatched in any of the current block explorers. You’ll notice in the screenshot below that deferred transactions are displayed, along with the amount of time until the transaction has been deferred by.
As well, it shows all traces of a transaction. A good example of traces is seen when exploring a `claimrewards` transaction. This one transaction is made up of 6 inline actions and 10 notifications.
We will continue to create articles that detail more of the features that eosq offers to anyone who is looking to retrieve the details of the blockchain. If you have any questions, please join the conversation in our dfuse Telegram channel.