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.
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
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.
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