Bitcoin Forum

Alternate cryptocurrencies => Altcoin Discussion => Topic started by: phil9 on May 23, 2018, 07:41:22 AM



Title: Documentation for building an online block explorer ?
Post by: phil9 on May 23, 2018, 07:41:22 AM
Hello,

I would like to build and share a block explorer for an existing altcoin.

I've already been able to build a local explorer on Ubuntu 16.04 using Iquidus (https://github.com/iquidus/explorer), everything is working fine, including crontab.

Now I'm looking for some documentation on how to "share" this block explorer. The altcoin has its own website, I would like to include an explorer to it. Are you aware of any documentation/tutorial that would help me going through the process ? I'm not very familiar with VPS, is this where I should build the daemon and then the explorer ?

Many thanks in advance for the help !

Phil


Title: Re: Documentation for building an online block explorer ?
Post by: FluVirus on May 24, 2018, 12:01:50 AM
I could help with getting your block explorer setup. You can also request an explorer at https://altexplorer.co/


Title: Re: Documentation for building an online block explorer ?
Post by: phil9 on May 24, 2018, 07:39:05 AM
I could help with getting your block explorer setup. You can also request an explorer at https://altexplorer.co/

Thank you very much for your reply Fluvirus.

Didn't know about altexplorer, thanks for the tip.

Actually what I'm looking for is really my own block explorer that would be "uploaded" (not sure this would be the correct word to use) on the altcoin website (for CSS matters), with the altcoin domain name (just as those explorers found on google : https://explorer.snowgem.org/ / http://explorer.steneum.com/)

I honestly have no clue on how this should work, as the process is still a bit unclear to me.

I know there is a settings.json file to be edited, especially the address for which I mentioned 127.0.0.1:3001. This allowed me to watch the explorer on my local machine (actually something went wrong overnight as I cannot connect anymore to 127.0.0.1:3001, but that's a different issue that I will try to solve...)

So any suggestion / general remarks on how to achieve the task would be much appreciated ! Feel free to PM me if you prefer.


Thanks again,
Phil