If you've ever developed an EOSIO smart contract, you might have seen the print statement which prints some output directly to the standard output pipe of nodeos. Well, you can now access that data through dfuse, and view it on eosq at the action level. 

When debugging a smart contract, it is very important to understand the notifications and inline actions that it generates, but more importantly, the order in which they are generated. eosq, which is built atop dfuse, is adding a new viewing filter to help developers with their deep-level questions.

The ability to quickly and efficiently sift through the billions of data points generated by the EOS mainnet cannot be underestimated. Powered by dfuse, the eosq block explorer now offers a contextual search, a unique-to-EOS feature, making it even easier to find the data users seek on a blockchain.

Delivering the most advanced search capabilities for any blockchain, dfuse Search brings tremendous power to eosq. This means that non-developers can now have quick access to the deep knowledge that only dfuse can offer.

Until now, there has been no way to search through the entire transaction history on a public blockchain with the power of a modern search engine. Block explorers have been limited to looking up individual transactions or accounts by ID. But now, thanks to dfuse, the contents of a blockchain are easy to search.

We’d love to share new features we’ve been working on for eosq - the high-precision block explorer. Some are game changers for developing on EOS, yet some are subtle in the UI, or are shown only in certain transactions. We’d like to highlight them since they will make developing on EOS much easier.

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.