B&C Explorer upkeep concern

@JetJet13

Blockexplorer is not loading at the moment seems some sort of server issue.

Hey @Dhume,

I just tried connecting, and it worked. I think you are trying to connect through https. http://bcblockexplorer.com should work.

Ah yes that was the problem, thanks!

block explorer is stuck. @JetJet13

block 652945 and its payload tx data are missing on the explorer. @JetJet13

    "hash" : "d3d7031b3341251bd56ed55be42800ee62689bb5f858215e068b85ff869d673b",
    "size" : 73650,
    "height" : 652945,
    "version" : 1,
    "protocolversion" : 5000000,
    "merkleroot" : "0eb0ada0112cb9f9edf2aebfd76a875ebecca3fcfc637c04293263e411f36395",
    "time" : "2016-10-03 22:45:06 UTC",
    "nonce" : 0,
    "bits" : "1e069310",
    "difficulty" : 0.00059415,
    "mint" : 0.02,
    "previousblockhash" : "316629126ff8e581a666d17826f82e8538bae9152cb75772d4cb0fa2ca4fabcc",
    "nextblockhash" : "2c54f9147f2e31bb366eabb700a6f7eea37e18a24c6981b3937d4d9ba23a97d8",

I have noticed that the explorer has some txs missing and balances wrong before. Let me know if it was because for example bcexchanged decoderawtransaction rpc command can’t handle long tx. I have a script using curl to circumvent the problem (w/o kernel change)

Hey @mhps,

Thanks for the heads up on the missing block. I have made the fix.

@JetJet13 , bcblockexplorer.com has been down for more than a day. Can you restart it?

@mhps, thanks for the heads up.

I got an email about a week ago from digital ocean about some maintenance downtime for the bc-explorer server.

I’ll get it back up asap,
Cheers.

Ok, B&C Explorer is up and running.

1 Like

I seems only 13 nodes in B&C now, much less than 30 nodes a week ago, and I can only conenct to 1 node after I just deleted all files(except wallet) and start over , any problem? @sigmike.

EDIT: Now connected to 4 nodes.

I don’t think so, my full node is currently connected to 27 nodes.

1 Like

The explorer is stuck again.
@JetJet13 I see a lot of addresses have negative balance, possibly due to that the block in which these address received fund was missing. It seems that these in tx often has a high volume, hence a high number of tx’s. Could you look into it and hopefully fix it?

@mhps, thanks for the heads up.

I looked into the reason behind the explorer going behind and it turns out the parser was missing a corner case which was causing a backlog in non-parsed blocks. It’s been corrected.

As for the addresses, I did a query and found 3 addresses with negative balances, 8SJDZghQmMP6fwaUcGaNsapYzqPG5DxqV1
8N6Em7NpU93gB8j4VbLMozeF5ThP1SmHqQ
8dueh4ZZnifxdeVezqm8kEPEiiq2XZkdCa
I will investigate these at a later time due to personal commitments.

Cheers.

Edit: Formatting.

2 Likes