RPC error -32000: nonce too low

Last updated: September 16, 2026

At a glance

Cause

Every account has a strictly increasing nonce. A submission whose nonce is at or below the account's current value is rejected by the node: either the transaction was already included, or another one took that slot. Triport classifies this as a network-level answer and passes it through rather than retrying elsewhere, because a resubmission would be rejected identically.

Solution

1. Read the current nonce with eth_getTransactionCount at the pending tag and rebuild the transaction from it.
2. If you are broadcasting concurrently, serialise nonce allocation per address — two workers reading the same pending count is the usual cause.
3. Before resending, check whether your original transaction is already mined: a receipt means there is nothing to resend.
4. To replace a stuck transaction deliberately, reuse its nonce with a higher fee instead of taking a new one.

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32000,
    "message": "nonce too low"
  }
}