You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest blocks view doesn't provide as much information as we could
Expected behavior
The latest blocks view is rendered by querying the blocks API and sorting by the time in descending order, it paginates the results and allows the user to navigate to older blocks.
When the user is at the 1st page, we keep polling the server for new blocks, when the user is in another page, we don't poll the server for new blocks to avoid inconsistencies while navigating through the pages.
It would be useful to render the value transferred in each block.
Actual behavior
The latest blocks API returns the 10 latest blocks only, they are retrieved directly from the xsnd, hence, there is no pagination.
The text was updated successfully, but these errors were encountered:
The latest blocks view doesn't provide as much information as we could
Expected behavior
The latest blocks view is rendered by querying the blocks API and sorting by the time in descending order, it paginates the results and allows the user to navigate to older blocks.
When the user is at the 1st page, we keep polling the server for new blocks, when the user is in another page, we don't poll the server for new blocks to avoid inconsistencies while navigating through the pages.
It would be useful to render the value transferred in each block.
Actual behavior
The latest blocks API returns the 10 latest blocks only, they are retrieved directly from the
xsnd
, hence, there is no pagination.The text was updated successfully, but these errors were encountered: