Built-in Block Explorer

[bitjson]

Chaingraph should ship with an optionally-enabled block explorer which fully utilizes the GraphQL API. This would be useful for development and testing, bring more developers to the Chaingraph project, and make hosting a block explorer easier for new chains and test networks.

Historically, block explorers have not been good at handling or conveying information about chain splits, and this would be a good opportunity to demonstrate split-resilience with Chaingraph.

I'd prefer for the block explorer to use Remix. It should be simple to build the explorer as a static web application, but also shouldn't be difficult for advanced users to set up server side rendering and/or incremental static regeneration.

This should be built after or alongside #9.

If anyone would like to contribute to the design here, please feel free to post feature requests, UI ideas, or mockups below!

[bitjson]

Related: "accelerated columns" #29 is likely important for ensuring good performance of expensive queries, especially for block explorer instances that are made available to the public. Though even without accelerated columns, it should be possible to use the built-in explorer to explore the data on a private, local instance even if that instance has only the minimum required indexes.