Five New Data Fields on eosq
Powered by dfuse, eosq has recently increased the amount of information shown for a transaction, providing more granular data than any other block explorer. For EOSIO developers and power-users alike, if you want *all* the information, eosq is the only explorer for you.
DPoS LIB Num
This field will display what the last irreversible block was for a given block height. This value is normally around 325–350 blocks behind the head block. It has been seen to grow well beyond that, however that was mainly on testnets. Since many developers deploy first on testnets and use eosq to have a view into the deep data of the chain, we found this to be a very handy piece of data to have available.
Deferred transactions may fail when it is their time to be executed. As there is no guarantee that a transaction will execute when a Block Producer tries to put it in a block, it is useful to understand why it failed. There are two failure types, hard fails and soft fails. Both types are objective failures (a subjective failure would actually just Expire instead, as the transaction would be attempted by each Producer until passing its expiry time).
Easily search for failed transactions by using
status:hard_fail. As of recently, all queries will include an implicit
status:executed search term. This is to avoid assuming that all results have been executed, while some may have failed. Some users had been bitten by this assumption, so we wanted to make it extremely explicit when being returned results that contain failed transactions.
When analyzing deferred transactions, it is often helpful to know whether it was created by a user directly pushing it to the chain, or by a smart contract. The “Creation Method” field now provides a clear response to this.
In the above example, you’ll notice that the block number where this deferred transaction was executed was 54,674,487. However, this transaction was created in the previous block, from the execution of a smart contract (see the Creation Method field) triggered by the transaction ce40410fa7… It’s also worth mentioning that as the only block explorer to support deferred transactions, eosq also provides a link to the created deferred transaction:
With multisig accounts, it can take a bit of work to dig through and know which keys were used to sign certain transactions. We’ve simplified this and displayed all keys that were used to sign a transaction to allow you to easily trace the approving signers.
You’ll also notice the Contextual Search magnifying glass in the above screenshot at the end of the public key. We have these magnifying glass icons scattered throughout eosq, providing you with a quick and easy way to create a contextual search. In this specific example when you click the icon, it will create a search that will look up any moment where that public key was attached to an account. To our knowledge, this is the only way to perform a historical query of a key through the chain. This would allow you to perform an analysis on which accounts intersect by ever having been controlled by the same user.
If you need a full picture of what is happening on the chain for each action, then eosq is the block explorer for you. If there are any other features that would improve your blockchain development experience, please don’t be shy to let us know.
Originally published at https://www.dfuse.io.