___|  _ \   |  |    |   |_ _|\ \     / ____|
 |     |   |  |  |    |   |  |  \ \   /  __|
 |   | |   | ___ __|  ___ |  |   \ \ /   |
\____|\___/     _|   _|  _|___|   \_/   _____| 

 --- A GOPHER-LIKE INTERFACE FOR HIVE BLOCKCHAIN ---

Gridcoin Open Source Block Explorer Released

BY: @neuralminer | CREATED: Oct. 5, 2018, 8:10 p.m. | VOTES: 69 | PAYOUT: $6.91 | [ VOTE ]

https://steemitimages.com/DQmUuA6Z9pX8cvdo7MekPG7cS7kFsXYKkh7Ugugc7mpUzZV/mc.png

Hey everyone,

I'm happy to announce that Gridcoin now has an open-source block explorer that you can run yourself, available on the official Gridcoin repo: https://github.com/gridcoin-community/BlockExplorer

If you're going to set up this explorer, I highly recommend using the autonode script to install/set up a wallet; it does all the legwork for you.

FYI, the initial importing of blocks into MongoDB will take a considerable amount of time.

If you want to see what it looks like, here's mine in action: http://GRCexplorer.NeuralMiner.io/

[IMAGE: https://cdn.steemitimages.com/DQmY1buKuw3Cfdudim31HdxNBiPmyA8p9arPmrmg9G9599C/image.png]

It currently runs in an Azure Standard D2s_v3 (2 vcpus, 8 GB memory) instance. I would suggest those specs as the absolute bare minimum (mine even runs a little slow at times).

If you have any questions, issues, or ways to improve the code, please feel feel to contact me or create an issue/PR on GitHub. I'm almost always available on the Gridcoin Discord (https://discord.gg/jf9XX4a), Slack/Rocket, or maybe even passing through your local grocery store.

NeuralMiner

TAGS: [ #gridcoin ] [ #grc ] [ #cryptocurrency ] [ #blockchain ]

Replies

@gridcoin-booster | Oct. 6, 2018, 1:49 a.m. | Votes: 5 | [ VOTE ]

This post received a courtesy vote from @gridcoin-booster! Thank you for your contribution to the #gridcoin community!

@jamezz | Oct. 7, 2018, 4:58 p.m. | Votes: 0 | [ VOTE ]

I will have to see how it likes 192gb vs 8 then

@neuralminer | Oct. 8, 2018, 1:32 a.m. | Votes: 1 | [ VOTE ]

The bottleneck is CPU, not memory; I'm currently only using 3 GB on one of the explorers. The more CPU you can throw at it during the import, the better. It calms down quite a bit after the import is complete.

[ BACK TO TRENDING ] [ BACK TO MENU ]
CMD>