Topic: CryptoCoin Explorer - Coin Block Explorers. - page 9. (Read 30831 times)
Thank you!
Progress on the networkhash api:
For now the improved api is only on the JKC explorer, i want to finish the time option before placing it on all the POW only chains.
Basic description:
The time function has not been implemented, it is next on the list.
POW/POS operability will be next after the time implementation.
Basically this api makes it easy to just get the network hash rate based on blocks or time.
For example:
http://jkc.cryptocoinexplorer.com/chain/JKC/q/getnetworkhash will return the current hash rate over the last 144 blocks.
http://jkc.cryptocoinexplorer.com/chain/JKC/q/getnetworkhash/100/1000?format=json will return the hash rate every 100 blocks for the last 1000 blocks in json format.
Both list and json are from oldest (START) to newest (current block).
For now the improved api is only on the JKC explorer, i want to finish the time option before placing it on all the POW only chains.
Basic description:
Code:
Shows network hash rate every INTERVAL blocks or time in minutes.
/chain/CHAIN/q/getnetworkhash[/INTERVAL/START/?format=[list,json,tlist,tjson]]
All parameters in [] are optional. Default is rate over the last 144 blocks in the list format.
START equals how many blocks or minutes back from current block to start.
list and json use blocks. tlist and tjson use time.
Both list and json order from START to current.
The time function has not been implemented, it is next on the list.
POW/POS operability will be next after the time implementation.
Basically this api makes it easy to just get the network hash rate based on blocks or time.
For example:
http://jkc.cryptocoinexplorer.com/chain/JKC/q/getnetworkhash will return the current hash rate over the last 144 blocks.
http://jkc.cryptocoinexplorer.com/chain/JKC/q/getnetworkhash/100/1000?format=json will return the hash rate every 100 blocks for the last 1000 blocks in json format.
Both list and json are from oldest (START) to newest (current block).
MNC - MinCoin really has to be added do your list 
which amount of BTC should donate for this coming alive??
which amount of BTC should donate for this coming alive??
Hi dreamwatcher, can you please add PXC?
I am more interested in relative hashing and perhaps nethash will get that as well. For example, I want to see hash rate increases over the hour or so....I already have a PHP script to scrape nethash (as the json output seem to miss the nethash number), so maybe that is the more accurate way to go.
How about if the getnetworkhash API accepts two integers. Both for hours, one for hourly interval and the other for how many total hours.
Output would be a simple list of hash rates with no extra information (unlike nethash).
For example:
getnetworkhash/1/24
would give a list of 24 hash rates, 1 for every hour in the last 24 hours.
223345566
225676778
234455667
221334454
etc...
This gives the option of getting hash rates based on time rather then on number of blocks.
Perhaps a third option to determine if the calculations would be independent or cumulative with the proceeding hours on the list.
Note: Just an FYI to everybody, I have mentioned this before but it should be mentioned again.
Do not use nethash for hash rates on PPC based coins (POW/POS) as it will be highly inaccurate due to the difficulty differences between POW/POS. This is one of the issues I am working on solving in the design of this new API.
I am more interested in relative hashing and perhaps nethash will get that as well. For example, I want to see hash rate increases over the hour or so....I already have a PHP script to scrape nethash (as the json output seem to miss the nethash number), so maybe that is the more accurate way to go.
Update on the network hash rate API.
The way the Network hash rate is calculated between ABE (nethash) and the daemon (getnetworkhashps) are significantly different and will come up with different numbers.
The daemons by default only use the blocks since the last difficulty change.This cannot be used on PPC difficulty based coins, so those are out of this calculation. The number is hard coded and can be changed easily. However, I somewhat question the accuracy as the sample size can be incredibly small until some time has passed since the last change. I have also noticed that getnetworkhashps does not appear in the Bitcoin daemon, perhaps this is why.
ABE (nethash) uses an average difficulty over the interval set in the url. Once I have the POS/POW difficulty issue worked out, this will work great for the PPC based coins. I am also thinking of changing getnetworkhash explorer API I implemented yesterday on some coins, to one using the ABE(nethash) instead of the daemon getnetworkhashps.
What do you think?
The way the Network hash rate is calculated between ABE (nethash) and the daemon (getnetworkhashps) are significantly different and will come up with different numbers.
The daemons by default only use the blocks since the last difficulty change.This cannot be used on PPC difficulty based coins, so those are out of this calculation. The number is hard coded and can be changed easily. However, I somewhat question the accuracy as the sample size can be incredibly small until some time has passed since the last change. I have also noticed that getnetworkhashps does not appear in the Bitcoin daemon, perhaps this is why.
ABE (nethash) uses an average difficulty over the interval set in the url. Once I have the POS/POW difficulty issue worked out, this will work great for the PPC based coins. I am also thinking of changing getnetworkhash explorer API I implemented yesterday on some coins, to one using the ABE(nethash) instead of the daemon getnetworkhashps.
What do you think?
Add TLC!
Is the same derived from getmininginfo?
Unfortunately not.
There are two issues that I need to deal with:
TRC,FRC and BTE, should be a relatively easy fix. I just need to drop in the getnetworkhashps RPC command object and adjust for the different difficulty target times.
PPC,NVC and BTB are going to be a bit more complicated.
These coins have POW and POS blocks with different difficulty formulas, though I can get the current blocks POW and POS difficulty with getinfo, I have no way of directly getting what the POW target of a past POS block was. The basic hash rate formula ((Difficulty* pow(2.0, 32)) / timePerBlock), needs at a minimum an accurate average of difficulty in this situation.
The difficulty difference between POW and POS blocks is so great, that an accurate average of POW difficulty without knowing what the POW difficulty on a POS block would have been, makes this calculation using this formula impossible.
I have a couple of ideas to get around it:
1. Every new block triggers an update to the explorer. I could do a getinfo inquiry at that time and record the POW difficulty. Network hash rate could then be calculated from those records.
2.Find or figure out a way to get the POW difficulty from a POS difficulty.
I will continue to work on this today, and hopefully come up with an answer.
Is the same derived from getmininginfo?
I know your site and many other sites that use CCE for information do not run daemons.
Thanks! FYI - you still don't have all the coins I run on your explorer
OK, I have the new API command coded and running on the JKC explorer:
http://jkc.cryptocoinexplorer.com/chain/JKC/q/getnetworkhash
I work on patching the others..
Well, the patch has been apllied to all the explorers, execpt there is a snag.
Not all the daemons support the "getnetworkhashps" function.
Namely: PPC,TRC,FRC,BTE,NVC and BTB.
However, I will look into patching those daemons, and give a report in a bit.
Awesome! - donation sent again!
I know your site and many other sites that use CCE for information do not run daemons.
Thanks! FYI - you still don't have all the coins I run on your explorer
OK, I have the new API command coded and running on the JKC explorer:
http://jkc.cryptocoinexplorer.com/chain/JKC/q/getnetworkhash
I work on patching the others..
I know your site and many other sites that use CCE for information do not run daemons.
Thanks! FYI - you still don't have all the coins I run on your explorer
Anyone know of a good way, in PHP to parse out the current network hash per second from CryptoCoin Explorer (thru the API)?
Almost all the daemons have a rpc call for that now (getnetworkhashps).
I know your site and many other sites that use CCE for information do not run daemons.
However, on the surface it seems trivial to add an API command to grab that information, especially since the newer versions of ABE can directly access the daemon RPC to get the memory pool.
I will look into it and get back to you.
Anyone know of a good way, in PHP to parse out the current network hash per second from CryptoCoin Explorer (thru the API)?
I have updated the theme to the home page. www.cryptocoinexplorer.com
A matching theme has been applied to the JKC explorer jkc.cryptocoinexplorer.com
I plan on applying this theme to all the explorers.
If anybody has any tweaks or comments, let me know. Even if you just hate it and think I am an arse for changing it
A matching theme has been applied to the JKC explorer jkc.cryptocoinexplorer.com
I plan on applying this theme to all the explorers.
If anybody has any tweaks or comments, let me know. Even if you just hate it and think I am an arse for changing it
WDC has been removed from CCE.
Why?
WDC has been removed from CCE.
Jump to: