Is there an existing issue?

• I have searched the existing issues

Description of bug

When the mempool receives multiple transactions from the same account, it currently fails to handle cases where a transaction with nonce (x+1) arrives before the prerequisite transaction with nonce (x). This results in an "invalid nonce" error for the (x+1) transaction.

Expected Behavior:
The transaction with nonce (x+1) should remain in the mempool in a pending state until the transaction with nonce (x) is received and successfully executed. Once the (x) transaction completes, the system should automatically process the waiting (x+1) transaction in the correct sequence.

Steps to reproduce

1. Identify current nonce (n) for a account (maybe a devnet account)
2. Submit a transaction with nonce (n+1)
3. Observe immediate rejection instead of queuing