[Bug]: Transaction count excluding relayed

[Jotenks66]

Contact Details ( Optional )

@joaquimTirach

Description

The explorer queries the number of transactions to generate the number of tx pages. Since the txCount doesn't take into account the transactions where the address is the relayer, it generates too few pages.

Steps to reproduce

Head to the explorer.
https://devnet-explorer.multiversx.com/accounts/erd18taz9feuez07qew9zu48yxk98p9x0h7m0y8mdtmjreyfwpnzekkqvtrr7f

Since the api responds with 221 txCount (at the time of writing), it generates 221/25 -> 9 Pages.

In reality there's hundreds of relayed transactions so the explorer only displays the 225 latest transactions, omitting the ones after that.

On which network is the bug manifesting itself?

Devnet

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[bogdan-rosianu]

Thanks for pointing this out! I prepared a fix on the API level here: multiversx/mx-api-service#1496

[Jotenks66]

Thank you very much @bogdan-rosianu!

It might be worth discussing if txCount also includes relayed ones?
Since everything that isn't relayed would increase the nonce anyways right?

This endpoint: https://devnet-api.multiversx.com/accounts/{address}?withTxCount=true

[bogdan-rosianu]

We would like to keep a separation between regular sending/receiving and relayed transactions. For example, the /accounts/{address}/transfers/count only includes the relayed transactions if a specific flag is set to true. So in a general purpose field like txCount I would say that relayed txs shouldn't be included by default.