The issue is that in one call a transaction is being given the number 2484376:

But in another call that transaction is being given the number 2484378:

So I agree it's not a case of new transactions interspersing themselves inbetween the existing transactions since, as you say, new transactions are added as the end and the loading is backwards.

It's some kind of re-indexing issue. Perhaps indirectly caused by new transactions being added forcing a re-indexing? It needs to be something that mainly affects larger accounts (which typically have more frequent transactions).

Or the call being directed to a different source which has different numbers. A different node somehow? My knowledge of how the API returns are actually generated is sketchy.

Posted Using LeoFinance ^Beta