There is an old explorer out there on the wrong fork. Please check and be sure you are not getting your data from a an explorer on the wrong fork (KGW hit at block 450k). Current block is around 459k; bad fork is around 470k. Cryptexplorer.com is correct. suggest using this explorer, or Chainz.

New explorers are online. Here are the links to machine readable info for Uno, in case you need them.

@FallingKnife Thank you for info, I will update it in a sec. Edit: I was already using cryptexplorer, no harm done

@henryjames1003 Lately I am only adding coins on demand or when I see something with big volume like URO. I will be very occupied till the end of august, until then please do not hesitate to request any coins that are on supported exchanges.

Edit: I will switch all chacha13 coins to chacha14 tomorrow morning, as I will be going away for the weekend. Not sure, at which hour the coins are going to switch for real tbh.

its really great your site and very useful for me.But for some coins, I spotted a huge difference between numbers of your site and that of CoinWarz, here is an example:(those 2 pages/screenshot are gerenated at the same time)

I am glad that you got the same results for all the main stats, like difficulty and block reward. Now about nethash.I got asked about that in the past - my explanation should be somewhere in the thread.

Basically coinwarz and every other coin site that relies on wallet data will give you nethash straight from the wallet(should be most precise).WTM and alike that rely on blockchains and pools to get the data, will extrapolate it directly from difficulty.

In theory both numbers should be the same, but sometimes they arent.I have looked around and I think why its wrong in this case. While ago we had a conversation here about block_time generations.

Now if you get true hashrate of 8,82 and multiply it by our error factor: 8,82 x 7,65 = 67,47. Pretty close aye?

I cannot explain why naut blockchain is generating blocks slower than it should be - basically diff is too high for current nethash. I see that naut has digishield - former speaker about block_time generations pinpointed the issue to this retarget algorithm.

I might be wrong here, but I think that if the wallet hashrate is 8,82 and the error factor is 7,65, the 'real hashrate' would be 8,82 / 7,65 = 1,15 GhsThis would explain the block time generation for the network is 7 minutes 39 seconds, instead of 1 minute, because the real nethash is too low for the current difficulty.I just check http://liteshack.com/?coin=naut, and at this site, the nethash for NAUT is around 1,9 Ghs at the time at this writing, not too far from 1,15 Ghs

I really doubt that. Wallet calculations are very precise, as they take last "N" number of solved blocks, compare their generation intervals and get a mean value from that. It means that they are free from any error factors - they truly represent hashrate power being target at a certain blockchain(still in the past).

It is far more plausible for me that liteshack devs are aware of the issue and tried to compensate(but got it wrong and are decreasing nethash). I mean there is no real way of calculating current net_hash.Absolutely none. You can only compare difficulty of a past block with its time_since_last_block and go from there.

EDIT: Or they have a formula for each coin to lower nethash by the amount of "current_block_time / target_block_time" - It would make sense, as it would make their nethash calculations more precise. Unfortunately in this case its working in their disadvantage, as the diff_retarget is faulty and they(as I do) assume it works perfectly.

By that argument I conclude that the real nethash for naut is in fact around 8,82 and the diff should be 7,65 times smaller to allow 1 minute block_time.

EDIT2: I think my explanation may not seem right at the first sight so here is an example:Everything goes back to normal and naut has 1 minute block_time blocks. To achieve that either diff goes x7,65 smaller or hashrate x7,65 higher. Lets take first case.

Diff goes x7,65 smaller -> Coinwarz stays the same, as their calculations reflect the true state of blockchain. WTM now gives you x7,65 smaller hash rate, cause diff is smaller. Liteshack does not lower their nethash by x7,65 cause block time is right on target ( current_block_time / target_block_time = 1 ). Every site reports the same nethash.

Lately I have only been doing maintenance and adding coins on requests, plus some backend improvements invisible to visitors.Added adaptation for 750ti cards.Thinking about adding config switcher, up to 5 sets of values for different kinds of your miners.

Dont hesitate to ask for coins/algos here, on pm, on twitter and through contact page