Quickblocks (A way of monitoring and summarizing data for any Ethereum address

Quickblocks is an easy way in which is used in monitoring and summarizing data for any Ethereum address faster that you would ever think.

This aspect of quickblocks Provides open source software libraries and tools for developers and accounting, auditing, monitoring solutions for the rest of us.

source

QuickBlocks this particular platform relies between a locally running Ethereum node and delivers the Ethereum data to your application.

There are two significant improvements to this platform(web3.js)path however. First, QuickBlocks caches the data locally which means that the 20 hours mentioned above is reduced to few minutes. Secondly, if you provide QuickBlocks with the ABI to your smart contract, it can deliver what we call articulated data.

What is web3.js ?

web3.js this is a collection of libraries which allow you to interact or communicate with a local or remote ethereum node, using a HTTP or IPC connection.
source

In other words, the web3.js library delivers nearly identical data as is retrieved from the RPC interface,and with this makes it difficult for any, but the most well versed in the data to easily use it. But with the presence of QuickBlocks stands between the node and your application improving the data significantly and this can be done in two ways:

it is faster
it’s translated into the language of the smart contract.
Differences between Quickblocks and web3.js

Quickblocks like I mentioned earlier is a node aplication that is faster and alsi havw a better data than web3.js.

QuickBlocks uses the same process and technique to acquire the data from the Ethereum node (RPC interface), it does so with two significant ways to improve. First, QuickBlocks caches the data client side. This means that subsequent retrievals are significantly faster.

The second improvement is that QuickBlocks can translate the data back into the language of your smart contract.

Where you can get the Quickblocks dapp
source

Functions of the Quickblocks

Quickblocks requires a database "cache"which you may store on any hard drive or probably an SSD drive.The QuickBlocks cache allows us to return data between 50 and 100 times faster than one can retrieve the same data through web3.js and the RPC alone.

Quickblocks also is able to parse and “articulate” the data returned by the RPC, so that you get votes and proposals and onTokenPurchase events which is done by the articulated data.

Quickblocks also requires block_list.
During this process many of our tools take a block_list as a command line parameter. A block_list may appear to be one or more valid block numbers (hex or integer), a range of valid block lists, one of a list of customizable special blocks such as ‘byzantium’ or any combination of the above Is done while performing this process.

Quickblocks also requires trans_list for this process this list in other words is some how related to the block_list. This in any way comes in many forms and is used by various of our command line tools.

A trans_list may be one or more transaction hashes, block numbers followed by a transaction index in the block, a block hash followed by a transaction ID (blockHash.transID), or any combination. trans_list is used in many tools.

For more enquires on the dapp you can visit

https://www.stateofthedapps.com/dapps/quickblocks