CryptoCoin Explorer - Coin Block Explorers.

[dreamwatcher]

Can anybody suggest a GOOD guide to making dynamically generated web pages mobile phone friendly?

There are plenty of guides out there, but I would like suggestions from anybody who has had to use one and found it worked great.

I figure if I am going to build from the ground up, this would be the time to make the explorers mobile phone friendly.

[defaced]

Hey bud, looks like the FRK Explorer is about 2k blocks behind.

[defaced]

Looks like its downloading the blockchain again, thanks bud! Sending you 25 FRK for your service.

[dreamwatcher]

Looks like its downloading the blockchain again, thanks bud! Sending you 25 FRK for your service.

Take a look at the PM I sent you. I need you to check the block chain and make sure something odd is not happening. 

[Taxidermista]

How about a phenixcoin explorer? Thank you!

[weav]

How about a phenixcoin explorer? Thank you!

http://explorer.phenixcoin.com/

[Miki77]

GLD CCE stop counting blocks.

[dreamwatcher]

Gldcoin daemon crashed, I have restarted it and the explorer is caught up.

Thank you for letting me know.

Robert

GLD CCE stop counting blocks.

[groll]

WDC chain stop at June 22. seems something is down or not synching correctly. should have lots of block since that time at 15 seconds each.


the other explorer for WDC is also down so, I have no way to see the chain as I'm looking around at how clean the coins are this is on my list of check.


BTW great job for the explorer work great for other coins.

One feature I would like is something to help find orphan. where a block has 2 next.  an example for Bitcoin is http://blockchain.info/orphaned-blocks this is where 51% attack can have occur and for ALT coin this is the most likely attack so anyone should be able to see it in the chain. (i can also see a simplified indication that just an icon when the next is multiple for a block and show the list of block as usual in batch of 20-50- with icon on those specific block ...) in fact should not have much when no attack occur or be in insta-mine mode.

[dreamwatcher]

WDC chain stop at June 22. seems something is down or not synching correctly. should have lots of block since that time at 15 seconds each.


the other explorer for WDC is also down so, I have no way to see the chain as I'm looking around at how clean the coins are this is on my list of check.


BTW great job for the explorer work great for other coins.

One feature I would like is something to help find orphan. where a block has 2 next.  an example for Bitcoin is http://blockchain.info/orphaned-blocks this is where 51% attack can have occur and for ALT coin this is the most likely attack so anyone should be able to see it in the chain. (i can also see a simplified indication that just an icon when the next is multiple for a block and show the list of block as usual in batch of 20-50- with icon on those specific block ...) in fact should not have much when no attack occur or be in insta-mine mode.

Well, it looks like the same daemon error has popped up  before at this point:

Code:

worldcoind: main.cpp:917: unsigned int GetNextWorkRequired(const CBlockIndex*, const CBlock*): Assertion `pindexFirst' failed.

This is with a fresh git clone and compile today.

I will look further into it, but if it is a daemon problem i will need an official git source to clone and compile to fix the issue.

[dreamwatcher]

I have rebuilt both the daemon and explorer databases for WDC and it appears to have cleared the issue.

I will continue to monitor the situation.

[dreamwatcher]

A question the the users of the APIs on CCE:

What if I were to make subscription service that would send a JSON request containing the information commonly used every time a new block comes on the network for that explorer.

For Example:

PPC has a new block on the network. This triggers a database update. How about if it also sends out to the subscribed, a JSON request containing the new blocks  height, difficulty, reward (when possible), network hash rate (again when possible) and other information determined by the dialogue here?

OR

Make it like a LP, where the explorer will send out a "ping" of sorts when a new block comes on the network and your sites can then request the information needed?

This would cut down considerably on the network "chatter" as no new information is available until a new block comes on the network and the explorer has stored the data.

Also, as mentioned above,  I also need to know what other information your sites use. Regardless of how and when the LP or auto send work out, I still want to make an API that will send the information commonly needed eliminating the need for multiple API calls.

[coinerd]

A question the the users of the APIs on CCE:

What if I were to make subscription service that would send a JSON request containing the information commonly used every time a new block comes on the network for that explorer.

For Example:

PPC has a new block on the network. This triggers a database update. How about if it also sends out to the subscribed, a JSON request containing the new blocks  height, difficulty, reward (when possible), network hash rate (again when possible) and other information determined by the dialogue here?

OR

Make it like a LP, where the explorer will send out a "ping" of sorts when a new block comes on the network and your sites can then request the information needed?

This would cut down considerably on the network "chatter" as no new information is available until a new block comes on the network and the explorer has stored the data.

Also, as mentioned above,  I also need to know what other information your sites use. Regardless of how and when the LP or auto send work out, I still want to make an API that will send the information commonly needed eliminating the need for multiple API calls.

Nice, a block explorer with push. I think it's a good idea for sure.

[sal002]

A question the the users of the APIs on CCE:

What if I were to make subscription service that would send a JSON request containing the information commonly used every time a new block comes on the network for that explorer.

For Example:

PPC has a new block on the network. This triggers a database update. How about if it also sends out to the subscribed, a JSON request containing the new blocks  height, difficulty, reward (when possible), network hash rate (again when possible) and other information determined by the dialogue here?

OR

Make it like a LP, where the explorer will send out a "ping" of sorts when a new block comes on the network and your sites can then request the information needed?

This would cut down considerably on the network "chatter" as no new information is available until a new block comes on the network and the explorer has stored the data.

Also, as mentioned above,  I also need to know what other information your sites use. Regardless of how and when the LP or auto send work out, I still want to make an API that will send the information commonly needed eliminating the need for multiple API calls.

I am for this - I assume I would need to have a callback script or something to accept the JSON push?

[dreamwatcher]

CraftCoin is on CCE. This coin is has been created to be used by the Minecraft game community.

crc.cryptocoinexplorer.com

[sal002]

Looks like the DigitalCoin explorer is down. 

[dreamwatcher]

Looks like the DigitalCoin explorer is down. 

Yep,

Server 2 went down.

I have restarted it and got the databases up to date.

This continues to be a resource issue, once the restructuring and rewrite are in place the resource issue will stop.

I have no ETA at this time, there is still much work to do.

[cosmoscoin-dev]

Please Add CosmosCoin(CMC) to CCE.

[dreamwatcher]

    
CryptoCoin Explorer III Development Updates.

https://bitcointalk.org/index.php?topic=262539.msg2804427#msg2804427

I believe a separate thread is needed for the development of CCE III, as it is a large project not only in the sense of CCE, but as a new development tool for other developers.

[dreamwatcher]

http://cryptocoinexplorer2.com:5555/

I have put up a live alpha/beta of Explorer III.

This is a PrimeCoin Explorer.

-At this stage only the basic explorer is online, none of the extra features are active yet.

-Search function is not implemented yet, however the URL scheme is simple, and searching by hand quite easy.

-There are a couple of known bugs - for example the transactions on some blocks do not show correctly.

-Spent output field in the transaction page is not implemented yet

This is strictly a testing stage, so expect the explorer to be up and down as bugs are fixed and features are added.