Thanks for the idea, yeah for now I am going to narrow my scope in filter like you said. Maybe in future updates the JSON will be changed up a bit, but no big deal. Still an awesome resource.

Hey, this is based on ruby where you can have any json structure you want, cause its getting parsed as a simple nested hash with key => value pairs.
Unfortunately its not possible to change the json structure now, hope you are good with your workaround

@Mikanoshi
All json calls without params will use the same defaults as seen in the UI.
For coins and asic you can check those by pressing defaults and for single calcs - reset.

Rewards increase differently from hashrate increase which is best observed on small nethash coins.
"BTC", "LTC", "SC", "BCH" will use current diff for single calcs and the rest uses 24h average.

Imagine a low nethash coin of 100Mh/s, where 1Mh/s could be produced by just one card.
You have 100 cards and throw all onto that coin.

Nethash has just doubled to 200Mh/s, diff raised. You now have 50% of nethash, but before you did that it was a 100% of nethash.

I'm looking on profitability calculator.

When I put 1000000.0 Mh/s (1Th/s), it shows daily reward as 0.086373 BTC ($710.65).
But when I put x10 = 10000000.0 Mh/s (10Th/s), it shows daily reward as 0.741514 BTC ($6,100.95).

I expect x10 power gives x10 reward, but it isn't the case.

Could someone explain those calculations?

Thank you and appreciate your feedback!

Same question as mikanoshi raised.
WTM treats the calculation as new hashrate added to the network.

@Mikanoshi
Vast majority of people is using it as a way to predict the future. (attempt at least)
Without this default, every calculation for a coin you are not already mining would be bogus.

Those people are stupid and doing things wrong
Profit calc is for checking your rewards, not predicting future, because it's impossible.
Let's say I was mining with 50% of nethash for the last 24 hours and then went to WTM to check my rewards, WTM shows 1.5 times lower values. Encouraging, but totally incorrect.
There should be at least an option to disable that.
How do you even calculate average nethash? Based on average diff you are calculating using questionable mathematically-unverified time-weighted method?
Nethash should be based on simple average diff (or sum of avg hashrates of ALL pools and somehow solo miners).

https://api.arabianchain.org/v1/dbix/main/network - this works

Actually the contact form is the right place for it, but I have made it for you and placed it into research queue.

Thanks for the direct link, but the difficulty is missing from the response.
Maybe explorer has some api to provide it?

Saved me some time, thanks