Sorry, my formulation was misleading ;)
The larger the number of samples taken to compute the average times, the smaller the range is within it varies. My request is to have a minimum range from 55 seconds to 65 seconds for the Y-axis so that I can see that the oscillation decreases if I choose a large number of samples for averaging.
Btw, would it be possible not to reset the range of blocks used (I mean the slider at the bottom) when I change the number of samples for averaging (upper slider)?
Hello.
I have updated the code on the githun so from version 0.1.1 this feature should be partially functioning +
the 2 things mentioned mentioned before are resolved.
The range is between 40 and 75 but when you change the averages block number calculation it scales from 55 to 65.
@patmast3r:
Please update the code when you will have time!
BTW: Is is possible for you to implement an API call to search blocks by block height too?!
Thanks.