Need to be able to get the average block time from the API

[BLuEScioN]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
In order to complete the new explorer blocks page I will need to be able to get the average block time from the API

Here is the blocks page explorer design where you can see I need to referenece the average block time

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[zone117x]

Can you please add a bit more detail to this request? Do you want a new endpoint that simply returns the average stacks block time over the last 24 hours (as indicated in the design image)?

[BLuEScioN]

@zone117x There are three ways that the explorer wants to use average (nakamoto) stacks block time:

1. Know the precise timestamp when a (nakamoto) stacks block was mined. In this case, the explorer will list the timestamp and the block time can be inferred from the block time. See image

2. The average stacks block time over 24 hours. We want to use this information just as you can can see in the 1st image.
3. Know what the average stacks block time was within a btc block. See image

For 1) I think this information can provided via the blocks api
For 2) an endpoint for the average block time in the last 24 hours would solve the problem at hand. Although having an endpoint just for this seems like one off work.
For 3) it would sense to include this information in the burn block api imo. Hopefully the work for 2) can be leveraged to solve for this case as well

[zone117x]

For 1) this should be ready, stacks blocks times were added a bit ago, but were accidentally left out of some of the endpoints, that was fixed in #1921 (we might need to deploy a new version for you to see the changes)

I agree for 2 and 3

[BLuEScioN]

This feature will not be public until we activate epoch 3 so I think we have some time to get this done. When do you expect we can fit this work in and what's your ETA for it?

[BLuEScioN]

Any update on 2 and 3?

[BLuEScioN]

@smcclellan Do you have any updates on this?

[zone117x]

I think we can have a MVP for this by end of week

[BLuEScioN]

@zone117x Any updates here?

[zone117x]

@BLuEScioN you were added for review on the referenced PR #1962