HI,
Received your PM and am responding here due to BTC talk being down.
To be honest there was never an issue, the explorer was not stuck. The block chain simply did not move for 10 hours between 245677 and 24568.
{
"hash" : "c10fe65d199b253b96ff339403a57739ab010501ca323c3a6083559789b617e4",
"confirmations" : 4,
"size" : 223,
"height" : 245677,
"version" : 1,
"merkleroot" : "e384f343ce559a944f8d4b3a7b51451a987daf72ed15e1e36f3ba01d606bc70c",
"tx" : [
"e384f343ce559a944f8d4b3a7b51451a987daf72ed15e1e36f3ba01d606bc70c"
],
"time" : 1430369616,
"nonce" : 2230978672,
"bits" : "1c027d19",
"difficulty" : 102.86492088,
"previousblockhash" : "09fa492663213441e5670fa8b03fd36f8b4b8597da80b92352135bf213b92016",
"nextblockhash" : "199dcd23b32f3717a35915a70cd42c4dd713bd3b7a12d74cbb02e2165b457948"
}
{
"hash" : "199dcd23b32f3717a35915a70cd42c4dd713bd3b7a12d74cbb02e2165b457948",
"confirmations" : 3,
"size" : 1885,
"height" : 245678,
"version" : 1,
"merkleroot" : "0b81ddf3ee439ed862d0307d7ebdc2a2ef1183f97a3121ae4b68deb7ba3b2fca",
"tx" : [
"3956da831a5432852e2a0166208e2f8f4ca06783dbe6aaf8b7f5fedc50003035",
"76b0f0d85ee586d57ab1c912dc47545a5e59c9b6d77cfb5474cc4d88a8ec68ef",
"0bf32da84ff1c6ecf5edced1d50030f09a416378127262e402f5e664301ae089",
"9efcd3b1829cccbc556a93445f7fd7d89d7648234055a9a99a81568c9b2145de"
],
"time" : 1430404983,
"nonce" : 3638004082,
"bits" : "1c027d19",
"difficulty" : 102.86492088,
"previousblockhash" : "c10fe65d199b253b96ff339403a57739ab010501ca323c3a6083559789b617e4",
"nextblockhash" : "c309c446f196abe1011c56b5e3351ab2938e714b462488b1ef70f910ae4d9de2"
}
1430404983 - 1430369616 = 35367 seconds / 3600 seconds per hour = ~9.82 hours
In the current code of the database loader there are two timers. One times each RPC request and times out at 10 seconds. The other times the main database loader loop and times out at 5 minutes. This is accomplished using a python module called Interrupting cow that wraps around the code. When either one these timers timeout, it completely exits (shuts down) the database loader after it raises an exception.
Currently the only way for the explorers to get stuck is if the coin daemon stops responding for whatever reason. However, the database loader will continue to start-up and try to parse blocks if the coin daemon continues to call it through block notify.
People will be able to see how all this works when I release the open-source version of CCE 4.0 (The current version in development). The database loader is ready to be released, and I have had a few developers take a peek at it.
In the mean time ,I have decided to release a full open source package including the web server. I am currently working on the web server at this moment.
The open source version of CCE 4.0 will be a very basic version. The closed source production version is more robust with many more features.
The open source version is meant as a foundation to building a full featured block explorer, though it can serve as an explorer on its own.
I will be releasing the open source version soon. The production version to be rolled out on CCE will come later, along with a new pricing structure and a ton more features.
