Skip to main content

Why Was My Crypto Transaction Reverted?

What Does Reverted Mean?​

A Reverted transaction was submitted and processed by the blockchain, but its intended action could not complete. The network rolled back the transaction's state changes, so a transfer, swap, approval, or contract action may not have taken effect.

The transaction remains part of the blockchain history. The network may still charge a fee because validators performed work before the execution reverted.

important

Do not submit another transaction until you understand why the first one reverted. Repeating the same request without changing its failing condition can produce another fee.

Reproduce and Verify the Status​

Use a transaction that already shows Reverted in Gem Wallet. Do not intentionally create a failing transaction for testing.

  1. Open Gem Wallet and select the asset involved.
  2. Select the reverted transaction from the activity list.
  3. Confirm that Status shows Reverted.
  4. Record the asset, amount, recipient or contract, network, date, and fee.
  5. Select View on explorer name.
  6. Verify that the explorer shows the same transaction ID and a failed or reverted execution result.

The blockchain explorer is the primary source for the public execution result. Different explorers may use labels such as Reverted, Failed, Error, or Execution reverted for similar outcomes.

Common Reasons a Transaction Reverts​

Smart-Contract Rules Rejected the Action​

A smart contract can reject a request when one of its required conditions is not satisfied. Examples include:

  • The contract is paused or the requested action is unavailable.
  • The wallet does not have the required token balance or allowance.
  • A staking, claim, or withdrawal condition has not been met.
  • The contract or function does not support the submitted parameters.
  • The on-chain state changed after the request was prepared.

Check the explorer's error or revert reason when it provides one. Do not rely only on the dApp's error message.

The Swap Conditions Changed​

A swap can revert when the market or pool changes before execution. Possible causes include:

  • The price moved beyond the allowed slippage.
  • The quoted route or deadline expired.
  • Available liquidity changed.
  • A required token approval was missing or insufficient.
  • The provider or pool rejected the route.

Request a fresh quote in Gem Wallet and review its provider, rate, minimum received amount, price impact, slippage, and fee. Do not simply increase slippage without understanding the effect.

The Transaction Ran Out of Gas or Network Resources​

Some networks measure execution with gas, energy, compute units, or similar resources. A transaction can be included but revert when it cannot finish within the available limit.

The network fee and execution limit are different values. Paying a higher price per unit may affect priority, while increasing an execution limit allows more work; neither fixes invalid contract logic.

Use Gem Wallet's current fee estimate for a new attempt. Avoid manually changing advanced fee settings unless you understand the network and the explorer's failure details.

A Nonce or Sequence Condition Changed​

Account-based networks process transactions using a nonce, sequence, or similar ordering value. Another pending or recently confirmed transaction can change the account state expected by a contract or dApp.

Check the wallet's activity and explorer history for earlier pending transactions. Wait for related transactions to finish before requesting a new quote or contract action.

Did the Asset Move?​

A reverted transaction normally does not complete its intended state changes. Verify the result instead of assuming:

  1. Check the explorer's token-transfer, balance-change, and event sections.
  2. Confirm the complete recipient or contract address.
  3. Refresh the asset screen in Gem Wallet.
  4. Compare the current on-chain balance with the wallet.

The network fee may be the only permanent balance change. If the explorer shows a successful transfer despite another failed step, record every related transaction before taking further action.

Why Is the Network Fee Missing From My Balance?​

Validators can charge for processing a reverted transaction even though the requested action failed. Gem Wallet displays the fee in transaction details using the network's fee asset.

For a detailed explanation and verification procedure, see Why Was I Charged a Network Fee for a Failed Transaction?.

Before Trying Again​

  1. Read the explorer's error details.
  2. Confirm the wallet, network, asset, recipient, and contract.
  3. Check the required token balance and native fee coin.
  4. Wait for related pending transactions to complete.
  5. For a swap or dApp action, request fresh data instead of reusing an expired request.
  6. Review any approval, amount, slippage, deadline, and fee again.

Only retry after correcting a specific cause. A higher network fee does not repair an invalid recipient, contract rule, expired quote, or missing approval.

When Not to Retry​

Do not retry when:

  • The request came from an unfamiliar dApp.
  • The contract or spender address does not match the intended service.
  • Gem Wallet or the explorer reports suspicious activity.
  • You do not understand what the transaction authorizes.
  • Someone claiming to be support asks you to repeat it or send a verification payment.

Close the dApp and follow What to Do After Connecting to a Malicious dApp if the request may be unsafe.

What to Provide to Support​

Open Settings > Support and provide:

  • The public transaction ID.
  • The blockchain network and asset.
  • The explorer's failure or revert reason.
  • The action you attempted and the steps that produced it.
  • The Gem Wallet app version.
  • A redacted screenshot of the transaction details.

Never provide your Secret Phrase or private key. See What Information Is Safe to Give Wallet Support?.

Reverted Transaction Checklist​

  • Confirm Reverted in Gem Wallet and on the explorer.
  • Read the public execution error.
  • Check whether any asset or approval changed.
  • Account for the network fee separately.
  • Correct the specific contract, quote, resource, or sequence issue.
  • Request fresh swap or dApp data before retrying.
  • Do not retry an unfamiliar or unexplained request.