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
When looking up address 0x6e57ae098ab06ecc491d688a255b64b61dd52dbb58d2cce46e7def6013ffc2cd clicking on >| goes to page 8202 but has txns before that (ex)
Later on, this changed so that it now goes to page 8246
Speculation
If we have an account with a lot of recent transactions (cached) and old transactions (pull from archive full node) would it occur that response we get is only from cache rather than all?
The text was updated successfully, but these errors were encountered:
This is because when you first go to the page, it'll cache the number of pages. If you do a hard refresh, it'll get the new transactions, and show them.
This happens when a lot of transactions occur in quick succession
When looking up address
0x6e57ae098ab06ecc491d688a255b64b61dd52dbb58d2cce46e7def6013ffc2cd
clicking on>|
goes to page 8202 but has txns before that (ex)Later on, this changed so that it now goes to page 8246
Speculation
If we have an account with a lot of recent transactions (cached) and old transactions (pull from archive full node) would it occur that response we get is only from cache rather than all?
The text was updated successfully, but these errors were encountered: