#blockchain explorers

Blockchain technology has taken the world by storm in recent years, revolutionizing the way we conduct transactions and store data. From cryptocurrency to supply chain management, Blockchain offers a secure and transparent solution for various industries. But what exactly is Blockchain? How does it work? And how can businesses benefit from its implementation? In this article, we’ll delve into the…

Found a new block-explorer script this weekend called "Ace" - it's the simplest form of a blockchain explorer, basically a PHP wrapper around JSON-RPC calls to a coin daemon.  Nice thing about that is that requires almost no setup - just adding your coin daemon's rpc port, user and password to a config file.  

There's no database attached so it's a very lightweight deployment, at the cost of having a smaller set of features.  

Abe and Insight each annoy me for their own reasons - Insight because Node kind of annoys me in general, and because their configuration is a little obscure, and Abe because it has no templating system to speak of so adding any extraneous info or customization requires sloppy hacks. 

TL; DR: There's a Transaction List for VTX but blockchain problems are preventing the deployment of other services. 

Building new software on a broken foundation is hard. 

Last week I attempted to set up a blockchain explorer for VvXx / Vortex using both Bitcoin Abe and Insight.  Each of these explorers was having different problems in providing a complete tool which would verify individual transactions, show the contents of a wallet, and allow a user to browse the block / tx history in a linear manner.  

I couldn't get Insight to correctly recognize the Genesis Block of the blockchain, so it was unable to retrive blockchain data.  Abe could retrieve the blockchain data, but considered every block beyond the first to be orphaned, so these couldn't be browsed through the web frontend. 

I tried setting up my own PHP script to make JSON-RPC calls directly to vvxxd.  I was able to get transaction details for individual transactions, but the block hashes returned by JSON-RPC didn't match the block hashes of the blocks that were read directly off the blockchain, so there was no way to match a TX back to the block in which it originated.  

Wallet addresses are also still coming up as "not on the network" even though RPC calls return valid-looking wallet addresses.