PendingTxs testnet

When using the klever websdk it seems my txs aren’t boardcasted to the testnet anymore. Can someone help me with this?

{
“data”: {
“firstPendingNonce”: 409,
“nonce”: 388,
“txPending”: 25
},
“error”: “”,
“code”: “successful”
}

If I use the Klever wallet app everything is fine but I can’t use it on the extension anymore. Any suggestions?

Forgot to tag @Duka . And now need 20 tokens to post something so i’m adding this :slight_smile:

Hello @SAME1 !

Looking at your account information, it seems that some of your transactions were submitted with nonces ahead of the current expected value.

Currently:

  • Your account nonce is 388

  • This means the next valid transaction must have nonce 389

  • However, your next pending transaction starts at nonce 409

This creates a gap between the current nonce and the next one being processed. The Klever node only accepts transactions in strict sequential order, so it will not process the ones starting at 409 until all previous ones (389 to 408) are submitted and included.

That’s why it looks like transactions are “stuck” — the chain is simply waiting for the missing nonces.


:white_check_mark: How to fix it:

I recommend sending a transaction manually using:

  • Nonce 389

  • If it goes through, it might trigger a chain reaction and unblock the rest

  • If not, you’ll need to manually submit transactions with nonces 390, 391, 392, and so on until 408


:warning: What likely caused this

If you’re using the Web SDK, it calculates the next nonce as:

nextNonce = currentNonce + txPendingCount

But in your case, because of the gap, it’s generating nonces like 413, which are invalid until all previous ones are processed.


:hammer_and_wrench: Recommendation

When sending large batches of transactions, manually manage and assign the nonce per transaction to ensure proper order. This will prevent gaps and pending states like this from happening in the future.

Let me know if you need help crafting or broadcasting the missing transactions — I’m here to assist

1 Like

Thanks @Nicollas that fixed it! :folded_hands:

2 Likes