Transaction errors explained

A transaction can fail in two places: the node can refuse it before it reaches a block, or it can run on the chain and fail there. Find your error below. Each page shows where it happens, the messages you will see, how to fix it and how it looks in a trace.

A transaction's path: the wallet sends it to a node, the node checks it, it enters the mempool and a block includes it. Errors in the first check (nonce too low, fee cap below the base fee, insufficient funds, intrinsic gas too low, replacement underpriced) stop it before the chain and give no hash. Errors after inclusion (out of gas, execution reverted) give a hash and a receipt with status reverted.A transaction's path: the wallet sends it to a node, the node checks it, it enters the mempool and a block includes it. Errors in the first check (nonce too low, fee cap below the base fee, insufficient funds, intrinsic gas too low, replacement underpriced) stop it before the chain and give no hash. Errors after inclusion (out of gas, execution reverted) give a hash and a receipt with status reverted.
The first group stops at the node. The second group costs gas.

Nonce and replacement

The order of an account’s transactions: a counter that must be used once, in order.

Gas, fees and funds

The node checks what the sender can pay before it accepts a transaction.

Reverts and out of gas

The transaction ran on the chain and failed, and still cost gas.

Missing the error you hit? Tell us which one, and we will add it: open an idea on GitHub.

Type to search the docs, Learn topics and the blog.