# Ethereum Transaction Pending? Speed Up, Cancel or Fix It

![Purple-and-lilac conceptual 3D cover: a Terenval Wallet-branded smartphone with an Ethereum transaction pending, a mempool queue, glowing blockchain route and ETH blocks. Displayed transaction controls are illustrative, not confirmed wallet features.](hero.webp)

**An Ethereum transaction is pending when it has been broadcast for inclusion but has not yet been recorded in an Ethereum block.** You may see “pending,” “submitted,” or “waiting for confirmation” for a simple ETH transfer, a USDC or USDT transfer, a token approval, or a DeFi swap. These labels do not prove the same thing. A wallet can remember a locally submitted action when an explorer cannot see it; a blockchain explorer may show an accepted transaction in its transaction pool; and an exchange can delay crediting a deposit even after the underlying Ethereum transfer has succeeded. **The first step is to establish which state is real—not to pay a higher fee immediately.**

Suppose you send ETH to a second wallet and the interface shows a spinner for 40 minutes. It is tempting to try the transfer again. But a second transaction with a *new* nonce could create an additional outgoing payment rather than replace the first. The right remedy may be to wait, use a wallet-supported **Speed Up** operation, attempt a **same-nonce cancellation**, or investigate an unrelated wallet display or exchange crediting problem. Those are fundamentally different actions with different risks.

> **Short answer:** If an Ethereum transaction is pending, first verify its transaction hash, correct network, sender and nonce in a trustworthy explorer. Check whether it is still unconfirmed, already included, or replaced. For an ordinary self-custody Ethereum transaction that is genuinely pending, you may wait or, if your wallet supports it, broadcast a higher-fee version with the **same sender and same nonce**. A cancellation usually tries to replace the pending transaction with a **0 ETH transfer to your own address using the same nonce**; it can succeed only if that replacement is included first. A confirmed transaction cannot be cancelled by this method. Do **not** send another full payment or expose a recovery phrase to a site claiming it can “unstick” the blockchain.

**Terenval's editorial assessment:** *A stuck transaction is not primarily a speed problem. It is an evidence-and-state problem.* People often spend extra gas while treating four independent issues as one: whether the transaction was **broadcast**, whether its **nonce** is eligible to execute, whether its **fee conditions** are competitive, and whether the **intended application outcome** has completed. This guide develops five original educational tools—the **Terenval Five-State Recovery Audit**, **Nonce Queue Map**, **Replacement Cost Ledger**, **Evidence-before-Action Gate** and **Gas Recovery Eligibility Ledger**. They help an individual make a verifiable decision; they are **not features claimed to exist inside Terenval Wallet**, an audited recovery service or a promise that lost crypto can be retrieved.

**Information cutoff: November 11, 2026.** Ethereum mechanics are described using the [official transaction lifecycle](https://ethereum.org/developers/docs/transactions/), [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559), [Ethereum's JSON-RPC reference](https://ethereum.org/developers/docs/apis/json-rpc/) and official wallet and explorer guidance. Terms for the two Terenval services come from their own published pages and are identified as product claims rather than independent findings. **Every amount, gas rate, ETH/USD exchange rate, waiting time and wallet balance used in an example below is hypothetical, not an observed network quote, typical user experience or guaranteed timeframe.**

## Key Takeaways

- **Pending is not failed.** A transaction that has not been included in a block does not yet have an on-chain execution receipt or an execution success/failure status.
- **Check the correct blockchain first.** A transaction on Base, Arbitrum or another EVM-compatible network will not necessarily appear on Ethereum Mainnet's Etherscan page.
- **A transaction hash is a tracking key, not proof of execution.** Signing and broadcasting can generate a hash before inclusion; different providers may show different views of a pending pool.
- **Nonce order matters.** A later transaction from a conventional Ethereum account can be queued behind an older unresolved nonce even if the later transaction offers more gas.
- **A speed-up is a replacement attempt.** It resubmits the intended action with the same nonce and a competitive fee; it does not give the original transaction a magical acceleration command.
- **A cancellation is a race.** Usually a higher-fee zero-value self-transfer competes for the same nonce. If the original lands first, the attempted cancellation cannot reverse it.
- **Do not confuse `maxFeePerGas` with the final price.** EIP-1559 transactions set fee caps; confirmed receipts report the effective gas price actually charged.
- **You normally do not pay for two versions of one nonce.** On one canonical chain, only one replacement candidate for that ordinary account nonce can be executed. But a replacement may cost more, and other unrelated transactions can still be charged.
- **A reverted transaction has already consumed gas.** Once a transaction executes in a block and fails, increasing its gas price afterward cannot erase the fee or undo its state.
- **“Dropped” is not a global forever-cancelled state.** A node may forget a transaction, which can later reappear if rebroadcast elsewhere.
- **Token and DeFi transactions have extra failure modes.** Pending approval, insufficient allowance, expired swap deadline and unfavorable slippage are different from a transfer simply waiting for inclusion.
- **Exchange and bridge delays are separate workflows.** On-chain inclusion, finality, bridge settlement and platform crediting are not interchangeable milestones.
- **Never paste seed phrases into a repair website.** A legitimate transaction diagnosis needs public addresses, transaction hashes and explorers—not custody of your private keys.
- **Cashback does not undo Ethereum's fee.** Under Terenval's published terms, an imported address may request 90% of qualifying *actually paid* Ethereum Mainnet gas fees from the previous 30 days, subject to eligibility and no duplicate reimbursement.
- **Gas Sponsorship is a different service.** It provides a request pathway for an imported Mainnet address that already holds tokens but lacks the ETH needed for an ordinary operation; it is not an automatic cancellation or universal transaction subsidy.

## What Does “Pending” Mean on Ethereum?

Ethereum accepts signed transactions into transaction pools maintained by network nodes before validators include them in blocks. A public pool is *not* one globally synchronized queue. Nodes use local admission, eviction and propagation rules. A transaction that appears on one explorer or RPC provider can be temporarily missing from another, and an application may show a locally submitted transaction that never reached a widely visible pool. The [Ethereum transaction lifecycle](https://ethereum.org/developers/docs/transactions/) describes the stages from a signed transaction and hash to broadcasting, inclusion, justification and finalization.

### Submitted, broadcast, pending, queued, confirmed and finalized

| Label | What it can establish | What it does **not** establish | Appropriate next check |
| --- | --- | --- | --- |
| Signed / Submitted | Wallet or app assembled or handed off a transaction | Public network accepted or mined it | Look for a valid hash and match the network |
| Broadcast / Pending | A provider or pool knows an unconfirmed candidate | It has succeeded or paid an execution fee | Check nonce, gas caps and current pool visibility |
| Queued | Candidate may wait for an earlier missing nonce | Paying more on this later nonce will necessarily help | Find the lowest unresolved sender nonce |
| Included / Confirmed | A block contains the transaction | A contract call necessarily achieved its intended result | Read receipt `status`, logs, gas and destination |
| Justified / Finalized | Stronger consensus assurances on included block | An exchange must already have credited a deposit | Check platform-specific policy and chain status |
| Reverted / Failed | Included execution returned failure under the receipt | Transaction remains pending or the network fee disappears | Read failure reason, state and actual fee |
| Dropped / Not found | Queried provider does not currently find a candidate | Every node has forgotten it forever | Cross-check hash, address, chain and same-nonce activity |
| Replaced | Different transaction with same sender/nonce was included | Both transfers executed | Identify winning hash and its receipt |

An [Ethereum JSON-RPC receipt](https://ethereum.org/developers/docs/apis/json-rpc/) is generally unavailable while the transaction remains pending. Once included, the receipt contains `gasUsed`, `effectiveGasPrice`, block information and `status` (commonly `0x1` for successful execution or `0x0` for failure). A block explorer may present these in more human-readable terms.

### A spinning wallet interface is not a consensus state

Wallet apps cache broadcasts, wait for their preferred RPC providers and sometimes refresh on a delay. A spinner can outlast actual block inclusion; an apparent “success” can also refer to a submitted request rather than completed settlement. Close and reopen the app if appropriate, but **do not use a local history refresh as proof that a transaction did or did not execute**. Check the explorer directly using the network and sending account shown in the transaction details.

### How long does an Ethereum transaction normally remain pending?

There is **no universal guaranteed pending duration**. Ethereum's block production is designed around approximately 12-second slots, but block production cadence is not a promise that a particular transaction with its existing fee caps will be accepted in the next slot. A transaction may be included quickly, wait through changing fee conditions, remain blocked by a nonce gap or disappear from one node's pool. The right question is **why this transaction is still excluded**, not whether an arbitrary ten-minute countdown has expired.

## Diagnose a Pending Ethereum Transaction in 60 Seconds

Before modifying gas or nonce values, establish facts that are independently testable. This first-pass workflow is deliberately conservative.

1. **Identify the network.** Determine whether the transfer was initiated on Ethereum Mainnet, Base, Arbitrum, or another network. Record its chain name and, for advanced users, chain ID.
2. **Copy the hash safely.** Use the wallet's transaction details; avoid links sent by strangers. On Ethereum Mainnet, open [Etherscan](https://etherscan.io/). On L2, use the explorer for that exact network.
3. **Check the public sender.** Confirm the explorer's `From` matches the wallet address you control; the recipient and token contract also matter.
4. **Read the status and block field.** If a block number and receipt exist, the transaction is not still waiting for first inclusion. If pending, look at gas caps and the nonce.
5. **Inspect the address activity.** Look for an earlier unconfirmed transaction, another hash with the same sender/nonce, or evidence of a completed replacement.
6. **Choose one action.** Wait; speed up the existing action using supported wallet controls; attempt a same-nonce cancellation; or contact an exchange/bridge when its separate workflow is the real bottleneck.

**Stop immediately** if a screen asks you to reveal a seed phrase, type a private key into a support chat, connect to an unfamiliar “rescue” contract or send cryptocurrency to an “unlock” address. Those demands are not part of ordinary Ethereum transaction diagnosis.

## Why Is My Ethereum Transaction Stuck? Seven Causes

### 1. The maximum fee is below the fee conditions required for inclusion

Under EIP-1559, a standard type-2 transaction carries `maxFeePerGas` and `maxPriorityFeePerGas`. If the block's required **base fee** rises above the transaction's maximum fee cap, the transaction cannot be included under those conditions. A cap that was reasonable at submission may become inadequate after a burst of demand. [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) specifies both the variable base fee and submitted caps.

### 2. The priority fee is uncompetitive

Even if the maximum fee exceeds the base fee, a low effective priority payment may leave a transaction unattractive relative to others. This is a market and inclusion-choice issue, not proof of a broken wallet. A higher tip can improve competitiveness, but does not guarantee immediate inclusion or make an unsafe transaction safe.

### 3. A lower nonce is waiting first

Conventional Ethereum transactions from the same externally owned account follow consecutive nonces. If account nonce 41 has not been included, a subsequent transaction with nonce 42 cannot simply overtake it as an independently executable sequence entry. The second action may display **queued** even with a generous fee cap. MetaMask's guide specifically advises resolving the oldest pending nonce first. See [MetaMask: why a replacement fails](https://support.metamask.io/manage-crypto/transactions/why-cant-i-replace-a-pending-transaction-/).

### 4. Broadcasting failed or only reached a limited provider

A locally signed transaction and a locally displayed hash are not proof of broad network propagation. Temporary RPC failures, application connectivity or provider policies can prevent a signed transaction from appearing on public explorers. A pool-dependent view is different from a canonical on-chain fact. Verify the address's history and independent network explorer before resending.

### 5. A provider dropped an underpriced or stale candidate

Nodes have limited transaction-pool capacity and their own replacement and eviction policies. They may remove low-priced candidates under pressure. Etherscan explains that [a dropped transaction](https://info.etherscan.com/transaction-dropped-replaced/) can reappear if rebroadcast. **A drop is not an irreversible on-chain cancellation**, because an unconfirmed signed transaction can remain with another node.

### 6. The sender's spendable ETH or transaction conditions changed

A user can have a visible ETH balance but insufficient spendable funds for the transaction value plus the maximum required gas allowance. Other pending transactions, a change in the account's current nonce or the data/contract rules can complicate rebroadcasts. A wallet may reject a transaction locally; a node may reject it; or a transaction may be included and later revert. Those cases require different evidence.

### 7. The blockchain action completed, but the application has not finished

An exchange may require additional confirmations or manual crediting. A bridge may need destination-chain execution, liquidity release or a challenge period. A swap interface may await an indexer or additional step. A user's app may show “pending” although Ethereum already included the originating transaction. **Do not repeatedly send tokens merely because an app's status indicator has not updated.**

## How to Check an Ethereum Transaction on Etherscan

Ethereum Mainnet's explorer is [etherscan.io](https://etherscan.io/). Paste the transaction hash or the **public** sender address in the search box. Be aware that a single hexadecimal hash only identifies a transaction on the chain where it was broadcast; a hash not found on Ethereum Mainnet may belong to another chain or may not have reached a public pool.

### The six fields that matter most

| Explorer field | Why it matters | Common mistake |
| --- | --- | --- |
| `Status` and block number | Separate pending from included success/failure | Equating “confirmed” with a successful token swap |
| `From` | Identifies the gas-paying account in ordinary self-funded transactions | Treating a received token as a fee paid by the recipient |
| `To` and contract interaction | Identify where the signed request was directed | Assuming a known app logo verifies contract authenticity |
| `Nonce` | Shows position in the sender's transaction sequence | Sending a **new** nonce when intending a replacement |
| Fee caps and effective gas price | Explain prospective inclusion vs actual cost | Multiplying `maxFeePerGas` by gas limit as a paid historical fee |
| `Transaction Fee` and `Gas Used` | Reveal included execution expense | Claiming cashback based on a never-included pending estimate |

### A confirmed transaction can still show a failed execution

A receipt with `status = 0x0` can represent a contract operation that was included but reverted. Its gas is a real network charge even though the intended token transfer or swap did not happen. A receipt with `status = 0x1` means the Ethereum execution succeeded according to protocol rules, **not** that the recipient was honest, the quoted exchange output was favorable or the desired off-chain service completed. [Ethereum JSON-RPC](https://ethereum.org/developers/docs/apis/json-rpc/) documents the receipt fields and statuses.

### What if the explorer says “transaction hash not found”?

First verify that the hash was copied in full, that the right network was selected and that the transaction actually came from your address. Search by sender address to find an alternate confirmed hash and its nonce. Try another reliable explorer or provider for the same network if needed. An absent hash alone does not justify copying the original payment into a new transaction. Check whether the local wallet history is stale or whether a same-nonce candidate was already included.

## Ethereum Nonces Explained: Why One Pending Transaction Can Block the Next

A **nonce** is the sender account's sequential transaction counter in ordinary Ethereum account transactions. For a conventional EOA, an included transaction consumes its nonce. Two candidate transactions from the **same sender** with the **same nonce** are alternatives for the same position in that account's sequence. They cannot both be included as ordinary sequential transactions in one canonical chain history.

### Terenval Nonce Queue Map — a reproducible diagnostic

Imagine a wallet whose next required on-chain nonce is **41**. The user submits a token approval at nonce 41, an ETH payment at nonce 42 and a DEX swap at nonce 43.

| Nonce | Submitted action | Candidate state | Can later nonces execute first? | Diagnosis |
| ---: | --- | --- | --- | --- |
| 41 | Token approval | Low-fee pending | No | Earliest unresolved action; inspect first |
| 42 | ETH payment | Queued | No | Increasing this fee alone does not resolve nonce 41 |
| 43 | DEX swap | Queued | No | Could expire or become economically unsafe while waiting |

The recommended order of diagnosis is **41 → 42 → 43**. If nonce 41 is replaced successfully with an ordinary self-transfer, the intended approval is not executed by that replacement. The payment and swap may subsequently become eligible to execute; **their original terms can still be unsafe**. In particular, a delayed swap can fail its deadline or become unfavorable. Resolving a nonce block does not authorize blind execution of everything queued behind it.

### What does “nonce too low” mean?

It often means the account's current included nonce has already advanced past the nonce used in the submitted candidate. Perhaps a replacement already won; perhaps another device submitted a transaction first. Check the on-chain account activity and included nonce before attempting another resubmission. A “nonce too low” error is not a request to increase gas for an already-consumed nonce.

### What does “replacement transaction underpriced” mean?

A node may refuse to admit a new candidate for a sender/nonce pair when the new fee parameters do not satisfy that node's replacement threshold. The [Geth command-line reference](https://geth.ethereum.org/docs/fundamentals/command-line-options) documents a default transaction pool `--txpool.pricebump` of **10%** for the relevant client configuration. **That is a client-policy default, not a universal Ethereum consensus rule or an assurance that exactly 10% always works.** EIP-1559 replacements may require sufficiently higher fee cap and tip in a particular wallet/provider path. Use the current trusted wallet's guidance and network conditions instead of blindly applying a fixed multiplier.

### Why the pending nonce reported by two RPC providers can differ

The [Ethereum JSON-RPC interface](https://ethereum.org/developers/docs/apis/json-rpc/) permits queries such as `eth_getTransactionCount` using `latest` or `pending`. A pending account count can incorporate that provider's local pool view and is not equivalent to an immutable on-chain state. A disagreement between RPC providers is therefore a clue about propagation or pool knowledge—not proof that one of them changed the blockchain.

## The Terenval Five-State Recovery Audit

Our original **Five-State Recovery Audit** converts a vague “stuck” message into a falsifiable next action. It makes the distinction between **on-chain evidence** and **wallet or platform display** explicit.

| State | Evidence | Best initial action | Unsafe shortcut to avoid |
| --- | --- | --- | --- |
| A — Not verifiably broadcast | Wallet claims submission, but hash not in credible provider/explorer and no receipt | Recheck chain, address, hashes and provider; diagnose local submission | Blindly repeat a large payment |
| B — Pending and nonce eligible | Visible unconfirmed candidate; no earlier missing nonce | Compare fee caps to current conditions; wait or consider supported replacement | Treating gas bump as a guarantee |
| C — Blocked by earlier nonce | Newer candidate queued behind lowest unresolved nonce | Inspect and resolve earliest nonce carefully | Raising fee of a later queued transaction alone |
| D — Included, success or revert | Receipt and block number exist | Inspect actual logs/fees; address application outcome or failure | Trying to “cancel” an included transaction |
| E — Chain complete, service pending | Underlying on-chain receipt succeeded but exchange/bridge/app step unfinished | Follow the platform's settlement/crediting process | Re-send the same tokens because of a spinner |

**Editorial rule:** An intervention is justified only after the current state is supported by the hash, sender, nonce and chain. If those facts disagree across tools, investigating the disagreement is usually safer than paying another fee.

## How to Speed Up a Pending Ethereum Transaction Safely

A speed-up usually means **replacing the candidate transaction with another signed candidate from the same account and same nonce**, often preserving the recipient, value and calldata but raising acceptable fee parameters. A supported wallet may expose a **Speed Up** button. The wallet assembles and broadcasts the replacement. The network is then free to include whichever valid same-nonce candidate it sees and selects first; the previous hash may later be labeled replaced.

### Step-by-step: use the wallet's native replacement function if available

1. Confirm the transaction is still pending on the **correct** network, with no included receipt.
2. Verify the sender, original nonce, intended recipient, amount and contract action. Reassess whether the original transaction is still desirable.
3. If the wallet offers a documented **Speed Up** control for this network and transaction type, prefer that to manual nonce editing.
4. Review the replacement's **same nonce**, fee caps, effective estimate, network and unchanged intended action before authorizing it.
5. Submit once, retain **both hashes**, and monitor which candidate was included. Do not assume the replacement won merely because its UI shows “submitted.”
6. If one transaction gets included, inspect the **actual receipt**; the other candidate cannot subsequently be executed under that consumed ordinary EOA nonce on the canonical chain.

[MetaMask's official pending-transaction guide](https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction) documents this approach for its own supported wallet flows. **That does not imply Terenval Wallet currently includes an in-app Speed Up button or manual nonce editor.** Users of a different wallet must check its actual documented controls. Do not expose a recovery phrase to an unknown replacement utility.

### Why paying more may not fix the real problem

If the candidate is queued behind another nonce, increasing only the later candidate's fee does not complete the earlier nonce. If the app has already issued a confirmed transaction, there is nothing left to accelerate at the on-chain inclusion stage. If a swap's underlying smart contract is designed to revert, a more competitive gas price can lead to a **faster failed execution**, not a successful one. Diagnosis should precede fee spending.

### When simply waiting may be rational

Waiting can be reasonable if the pending transaction is not time-sensitive, the sender's nonce sequence is understood, current fee conditions may normalize and no additional activity depends on immediate inclusion. Waiting also avoids a rushed replacement that could unexpectedly finalize an unwanted payment. But **there is no guaranteed future low-gas window**; if a token price or contract deadline is changing, the economic cost of waiting may outweigh a modest higher fee. The article's cost model below helps separate these factors.

## How to Cancel an Ethereum Transaction — and Why It May Fail

**A confirmed on-chain Ethereum transaction cannot be retroactively cancelled.** Before confirmation, a cancellation is ordinarily a *same-nonce replacement attempt* designed to consume the nonce with a different, innocuous action. A common pattern is **0 ETH from your account to your own address**, using the same nonce as the pending original and a fee sufficient for inclusion. That self-transfer still pays gas if included.

### What a standard cancellation attempt changes

A successful replacement self-transfer consumes the nonce that the original transaction wanted to use. The original ordinary EOA transaction can no longer execute in that nonce slot on the canonical chain. It does **not** return an already completed token transfer or undo a contract that already executed. It also does not cancel different pending transactions with **higher nonces**. See the [Ethereum.org support FAQ](https://ethereum.org/community/support/faq) and [MetaMask guide](https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction).

### Before attempting cancellation

Verify the original is genuinely unconfirmed. Identify exactly which **sender and nonce** it uses; ensure you control that account. If your wallet supports **Cancel** in its transaction screen, check its instructions. For manual cancellation, use only a compatible, well-understood signing interface with reliable nonce and EIP-1559 fee controls. If you cannot confirm these details, it is safer to stop and seek documentation than to improvise an unfamiliar raw transaction.

### Why cancellation is not guaranteed

The replacement and original compete. Some nodes may not accept your replacement because the fee bump is insufficient; some validators may include the original first; another node may retain the original signed candidate. If the original wins, you can neither negate it with a later self-transfer nor recover the protocol fee automatically. If the replacement wins, you pay its actual execution fee and the original does not also charge execution gas for that nonce. The order of observed broadcasts is not an inclusion promise.

### Special case: an unauthorized or suspicious pending transfer

If you did not authorize the transaction, focus on **key compromise** rather than assuming a gas change solves the threat. If an attacker controls the same keys, they can also issue valid candidates with competitive fees, observe activity and move other funds. Follow independent security guidance, consider a secure destination account and professional incident response where appropriate, and do not put more funds into an apparently compromised address merely to win a gas auction. Read Terenval's guide to [token approvals and revocation](https://wallet.terenval.com/answers/how-to-check-and-revoke-token-approvals-in-a-crypto-wallet/). A cancellation attempt cannot restore account security by itself.

## EIP-1559 Replacement Fees: Calculate the Actual Cost, Not the Cap

For an ordinary type-2 transaction, the sender can set two fee parameters: `maxFeePerGas` (the total per-gas price ceiling) and `maxPriorityFeePerGas` (the priority fee ceiling). The protocol also has a **base fee** for the block of inclusion. Assuming a valid transaction and an adequate fee cap, an explanatory expression is:

**Effective gas price = min(maxFeePerGas, baseFeePerGas + maxPriorityFeePerGas).**

**Actual execution fee in ETH = gas used × effective gas price (gwei) ÷ 1,000,000,000.**

The sender does **not** automatically pay `gas limit × maxFeePerGas`; that expression is an upper-limit-oriented budget check, not a confirmed receipt. For exact historical costs use `gasUsed` and the receipt's `effectiveGasPrice`. The specification in [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) and the [Ethereum gas documentation](https://ethereum.org/developers/docs/gas/) distinguish base fee, priority fee and maximum caps.

### Worked example: ETH transfer versus speed-up versus cancellation

Assume the user initially broadcasts an ETH transfer with **nonce 76**, gas limit 21,000, `maxFeePerGas = 30 gwei` and `maxPriorityFeePerGas = 1.5 gwei`. It remains pending; there is **no on-chain execution fee yet**. Suppose the network's current base fee is 20 gwei, and a proposed replacement uses a 45-gwei maximum fee and 3-gwei priority cap. For illustration, assume a block ultimately includes the replacement while the base fee is still 20 gwei.

| Candidate for nonce 76 | Max fee cap | Priority cap | Gas used if included | Effective price at 20-gwei base | Execution fee if included |
| --- | ---: | ---: | ---: | ---: | ---: |
| Original ETH transfer | 30 gwei | 1.5 gwei | 21,000 | 21.5 gwei | 0.0004515 ETH |
| Higher-fee same-payment replacement | 45 gwei | 3 gwei | 21,000 | 23 gwei | 0.0004830 ETH |
| Higher-fee zero-ETH self-transfer | 45 gwei | 3 gwei | 21,000 | 23 gwei | 0.0004830 ETH |

The candidate that **actually wins the same nonce** is the one that charges an Ethereum execution fee on the canonical chain. At a strictly **hypothetical ETH/USD rate of $2,500**, the 0.0004830 ETH replacement fee equals **$1.2075**, or about **$1.21**. If the original instead wins, its fee under the stated 20-gwei base and 1.5-gwei tip assumptions would be **0.0004515 ETH**, roughly **$1.13**. You do **not** add both execution fees just because both were submitted. Their gas caps do not prove either will be mined or that the higher-fee one necessarily wins.

A lower initial base fee could have produced a different result. If an earlier block had included the original at a **16-gwei base fee**, its effective price would have been **17.5 gwei** and the cost **0.0003675 ETH** (about **$0.92** at the same hypothetical exchange rate). The relevant base fee is the one in the *actual inclusion block*, not a quote from the time of drafting the replacement.

### A more expensive smart-contract replacement

A token swap that uses **180,000 gas** at a hypothetical effective price of **23 gwei** would consume **0.00414 ETH**, or **$10.35** at $2,500 per ETH. This is not the cost of a 21,000-gas self-transfer and is not a uniform DEX charge. Contract execution complexity, failure paths and calldata can change gas used. A separate token approval can add another transaction and another fee. A user should compare an intended swap's economic value, slippage and deadline with the cost and risk of a fee bump.

### Why the replacement quote can look much larger than the fee paid

Wallets often display maximum possible expenditure for sufficient funding and risk management. A 45-gwei cap at 21,000 gas suggests a **0.000945 ETH** per-gas-cap budget, but if the block base fee is 20 gwei and the priority paid is 3 gwei, the **actual** 21,000-gas fee is only 0.000483 ETH. This distinction matters both to budgeting and to future Cashback eligibility. The network receipt, not the cap, establishes past expenditure.

### Replacement thresholds are not settled by arithmetic alone

A numerical example can demonstrate execution fees but cannot guarantee *mempool acceptance*. Node transaction pool policies, the wallet implementation, how a provider treats pending types and changing base fees all influence whether a replacement candidate propagates and is selected. A 10% Geth transaction-pool price bump parameter should not be presented as a protocol-wide “safe 10% button.” See [Geth options](https://geth.ethereum.org/docs/fundamentals/command-line-options), [Geth pool inspection](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-txpool) and the supported [MetaMask replacement workflow](https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction) for the relevant environment.

## Terenval Replacement Cost Ledger: What Should You Actually Count?

The **Terenval Replacement Cost Ledger** is an editorial bookkeeping model. It separates an unspent quote, a replacement candidate and a *paid receipt*. It prevents double-counting alternative same-nonce transactions and prevents confusing an application's estimated gas with already lost funds.

| Record | Example | Count as already-paid Ethereum gas? | Why |
| --- | --- | --- | --- |
| Original pending hash | Nonce 76, quoted maximum 0.00063 ETH | **No** | Pending has no confirmed execution receipt |
| Replacement submitted, pending | Same nonce 76, fee cap raised | **No** | Broadcast does not create a receipt |
| Winning successful speed-up | 21,000 gas × 23 gwei = 0.000483 ETH | **Yes, if included** | Receipt proves the network expense |
| Losing original candidate | Same nonce, never included | **No** | It did not consume block execution gas |
| Successful cancellation self-transfer | 21,000 gas × actual effective price | **Yes, if included** | Zero ETH value does not mean zero network fee |
| Reverted DEX swap | Receipt with `status = 0`, gas consumed | **Yes, if included** | Contract execution failed but still consumed resources |
| Off-chain service fee | Exchange charges a withdrawal surcharge | **Not Ethereum gas by itself** | Separate platform expense, not the sender's Mainnet receipt |

**Analytical takeaway:** the right unit of historical evidence is **one included transaction receipt**, attached to a particular chain, sender, timestamp and transaction hash. A fee estimate belongs in a decision model, not a claims ledger. This distinction becomes especially important when investigating cashback for Ethereum Mainnet gas already spent.

## What to Do When an Ethereum Transaction Was Dropped or Replaced

A **dropped** transaction was previously known to at least some nodes but is no longer retained or observed in the queried pool. It may be dropped for fee competitiveness, pool limits or other local policy reasons; the network has not recorded a consensus-level “cancellation” for that never-included candidate. A separate node can still retain and rebroadcast a valid signed candidate. See [Etherscan's dropped/replaced explanation](https://info.etherscan.com/transaction-dropped-replaced/).

### The safe response to “Dropped”

Check the original public sender, the nonce, any newer candidate hashes and the latest included activity of the account. If the nonce has already been consumed on-chain, identify the winning transaction and stop trying to reuse the old nonce. If it remains unconsumed and you still intend the action, use a trusted wallet's documented resubmission flow with current estimates. If you no longer intend it, evaluate a safe cancellation attempt or wait, recognizing that the original may remain in some nodes' pools. **Not found on one explorer does not equal mathematically impossible to execute later.**

### The safe response to “Dropped & Replaced”

Find the replacement hash and inspect its receipt. If the replacement is a zero-ETH self-transfer, confirm it was executed from the **same sender** at the **same nonce**. If it contains the original payment, verify whether the expected asset actually arrived. If the replacement executed a different smart-contract action, investigate that action on its own merits. The old hash's status is not a sufficient receipt for the new hash.

### Can a transaction be both dropped and already finalized?

Not in the same meaning on one canonical chain: a transaction that has a finalized inclusion is no longer merely an unconfirmed pool candidate. However, explorer caches, stale wallets, incorrect networks and differing hashes can produce apparently contradictory labels. Use verified block numbers, final receipts, the sender's nonce history and the exact chain to reconcile them. Do not average conflicting statuses or choose the label that best fits your preferred outcome.

## Why an Ethereum Transaction Failed After Confirmation

**Failed** and **pending** are not interchangeable. If a transfer or contract call is included in a block and its receipt shows unsuccessful execution, the network has charged gas for work performed. Sending more priority fee cannot retroactively modify that receipt. A new retry may be a **different transaction with a new nonce** and potentially a second gas expense.

### Insufficient gas limit versus insufficient gas price

A **gas limit** restricts the total computational work available. A contract that runs out of gas during execution can revert and consume all gas made available, while some validation failures prevent a transaction from being included in the first place. A **gas price or fee cap** determines payment incentives and eligibility for inclusion. They solve different constraints: a gas price bump does not make an intrinsically undersized gas limit adequate; a larger gas limit does not fix a max fee cap below the required base fee. See [Ethereum gas documentation](https://ethereum.org/developers/docs/gas/).

### Smart-contract reverts, slippage and expired deadlines

DeFi applications can revert when trade conditions are no longer acceptable, a slippage bound is violated, token allowance is insufficient or a deadline has passed. A reverted transaction may be safely retryable only after identifying the cause and recomputing live quotes, balances, allowances and risks. **Never treat a successful receipt as proof that a token received is valuable or genuine**; the token contract must also be verified independently.

### Token approvals can be separate fee-bearing transactions

A swap may require one transaction to approve a token spender and another to execute the swap. If the approval is pending, the swap may wait for the spender allowance or may not have been submitted at all. If the approval succeeds but the swap fails, the approval may remain in effect, depending on contract semantics. Review permissions independently; [Terenval's approvals guide](https://wallet.terenval.com/answers/how-to-check-and-revoke-token-approvals-in-a-crypto-wallet/) explains why revocation can matter. An approval is not automatically a transfer of the token balance.

### Why repeating a failed payment needs caution

If the failed operation was an ordinary ETH transfer to an externally owned account, a receipt with execution failure is unusual and warrants careful validation of the contract context, gas or network. If the transaction targeted a contract, a retry may succeed under changed conditions or fail again for the same reason. Before any retry, reconstruct *what was signed*, *what executed*, *what receipt exists* and *what might still be authorized*. A rushed retry can turn one fee loss into several.

## ETH, USDC and USDT: Different Pending-Transfer Scenarios

### ETH payment pending to another wallet

Check the sender, recipient, transaction nonce and effective fee eligibility. If the transaction is still pending, assess whether the recipient should still receive the ETH. A speed-up tries to execute that same payment faster; a same-nonce self-transfer tries to stop it from executing. **Neither action will reverse a transfer that already has a successful inclusion receipt.** A fresh outgoing payment with the next nonce is not a replacement.

### USDC or USDT transfer pending on Ethereum Mainnet

USDC and USDT are ERC-20 tokens when used on Ethereum Mainnet. An ordinary token transfer requires ETH for the transaction's network gas. Check the specific token **contract address**, not just the ticker, because similarly named malicious tokens exist. The transaction may call a token contract and consume more than 21,000 gas. A successful token transfer should be confirmed using event logs or balance changes of the correct contract, not an ETH-value field of zero. On a wrong network, use that network's explorer and native gas asset instead.

### USDC sent through a centralized exchange

If an exchange broadcasts the withdrawal, the **exchange may be the on-chain sender**, not your personal deposit address. You might see a withdrawal marked “processing” while no public transaction hash exists. Once a public hash exists, inspect its chain and destination; after chain settlement, the receiving exchange may apply further crediting checks. The appropriate next action is often contacting that exchange with a verified hash, network, token and destination—not manipulating an unrelated self-custody nonce.

### A receiving wallet does not display the incoming token

Confirm the token contract and recipient address on the correct explorer. A token transfer can have succeeded while a wallet's interface has not indexed or displayed the asset. A new payment is not a fix for a visibility problem. Never import an unknown token by blindly trusting a link supplied in an unsolicited message; independently verify the contract and supported network.

## DeFi Swaps and Lending: When “Pending” Is an Application Problem

### Swap submitted, but the UI still says pending

Open the underlying transaction hash. If it is pending on Ethereum, gas and nonce diagnosis applies. If it was confirmed successfully, check whether expected tokens were received, the route's pool events and whether the app is waiting for an indexer or follow-up step. A confirmed swap can have an economically poor execution due to price impact, fees or adverse slippage; **paying additional gas afterward does not improve an already executed exchange rate**. Our [Slippage guide](https://wallet.terenval.com/answers/what-is-slippage-in-crypto/) explains these separate costs.

### A pending approval before a swap or DeFi deposit

The first action may approve an ERC-20 spender. The second action may be a swap, deposit, collateral change or withdrawal. Treat them as **different transactions**, each with a nonce, potential gas cost and security implication. An app may show one continuous progress indicator for a multi-transaction workflow. Check whether a later transaction was actually signed before saying it is “stuck.”

### Borrowing, repaying or liquidating a DeFi position

A loan can be time-sensitive. An unconfirmed collateral deposit or repayment may leave risk unchanged while the user's wallet still shows an optimistic pending state. Waiting, replacing or cancelling must be evaluated against market risk and liquidation thresholds. An increased fee might reduce one bottleneck but does not protect an undercollateralized position from price movement. Review the [DeFi Lending guide](https://wallet.terenval.com/answers/how-does-defi-lending-work/) before treating a pending loan action as merely a network inconvenience.

### Smart accounts, bundlers and account abstraction

Not every modern wallet action is a plain user-signed EOA transaction. Smart accounts may use **UserOperations**, bundlers, paymasters or delegated execution and can have different nonce mechanisms and off-chain lifecycle displays. A single user action can produce a later settlement transaction submitted by an intermediary. If your action uses these mechanisms, follow the **specific smart-account provider's** diagnostic tooling; do not assume that manually issuing an EOA zero-ETH self-transfer with a guessed nonce is relevant or safe. The ordinary same-nonce examples in this guide describe conventional EOA transactions unless explicitly stated otherwise; account-abstraction UserOperations and bundlers are described in [ERC-4337](https://ercs.ethereum.org/ERCS/erc-4337).

## Base, Arbitrum and Bridges: The Meaning of Pending Changes by Network

Ethereum Mainnet, Base and Arbitrum are different networks with their own transaction processing and explorer histories. A transfer that appears pending in an app must first be matched to its actual origin chain. **Do not apply Mainnet's observed base fee or a Mainnet transaction hash search to an L2 transaction** without verifying the chain.

### Ordinary transactions on Base or Arbitrum

If your action is an ordinary on-chain L2 transfer, check the L2's receipt and relevant sequencing/confirmation status. Some L2s have additional distinctions between sequencer acceptance, posting data to Ethereum and later L1 finality. Their gas pricing and replacement support may differ by provider. An interface's “confirmed” can refer to L2 execution rather than the entire protocol's finality. Use chain-specific documentation and the current official interface.

### The Ethereum-to-Arbitrum deposit completed on L1, but funds are still moving

A bridge can involve an **origin-chain transaction**, an L2 message and a **destination-chain result**. Inclusion of the first transaction does not prove final receipt. Track the bridge message through the canonical bridge's official tools and check the exact asset contract on the receiving network. An arbitrary extra ETH payment from the source wallet will not speed up a bridge message that is already following a protocol-defined settlement path. See the [Terenval cross-chain bridge guide](https://wallet.terenval.com/answers/what-is-a-crypto-bridge/).

### An Arbitrum withdrawal is waiting days: is it “stuck”?

A canonical optimistic-rollup withdrawal to Ethereum has a security challenge/finality workflow. [Arbitrum's official introduction](https://docs.arbitrum.io/get-started/arbitrum-introduction) currently describes a delay of roughly **6.4 days** for canonical L2-to-L1 withdrawal, rather than a near-instant ordinary transfer. The [L2-to-L1 messaging documentation](https://docs.arbitrum.io/how-arbitrum-works/deep-dives/l2-to-l1-messaging) explains the separate message-execution stage. Those details may change with protocol updates. A pending bridge **withdrawal finalization** should not be “fixed” by resending the original tokens or replacing a successfully included L2 burn transaction.

### Fast bridges: different delays and trust assumptions

A fast bridge can rely on external liquidity, solvers or different security assumptions. A destination-chain deposit may be delayed because of relayer, liquidity, risk checks or messaging conditions rather than Ethereum nonce congestion. Before escalating, record the origin-chain hash, bridge reference, target network, output token **contract**, recipient and whether any additional claim transaction is required. **Native USDC and bridged/wrapped representations may differ** even when their visible names look alike.

## Transaction Pending at an Exchange: What Customers Should Verify

A centralized exchange can display statuses such as “Processing,” “Broadcasting,” “Awaiting network confirmations,” and “Crediting” without using Ethereum's precise consensus definitions. Distinguish **custodial account bookkeeping** from self-custody on-chain state.

### Withdrawal pending before a hash exists

The exchange may not yet have broadcast a transaction, so there is no sender nonce you can personally replace. Check its authenticated withdrawal history and, if needed, contact official support from inside the platform. Never trust a stranger who claims to be able to “release” the exchange withdrawal after an upfront crypto transfer.

### Withdrawal broadcast with a public hash

Check the correct network, token contract and destination. If the on-chain transaction remains pending, the exchange's sending account usually controls any speed-up or replacement, not the recipient. A recipient who does not control the sender's signing keys cannot fix that sender's nonce through their own wallet.

### Deposit on-chain confirmed but not credited by the exchange

Verify the receiving address, token, network, required confirmations and any tag/memo requirements. Contact the exchange with the correct hash, block and token details. Gas price changes to your own address cannot retroactively make a custodial platform credit an already completed deposit.

## Terenval Gas Fee Cashback: Can You Recover Fees From a Failed or Cancelled Transaction?

**An Ethereum execution fee is final as a protocol expense once the transaction is included.** Ethereum does not issue a native refund merely because a swap reverted or a sender regrets its transaction. **Terenval Gas Fee Cashback is different:** it is a separately administered wallet program described on [Terenval's published program page](https://terenval.com/gas-fee-cashback/). The public terms advertise a request for **90% of eligible Ethereum Mainnet network gas fees actually paid in the previous 30 days**, for the imported address under review. That is a product offer conditional on eligibility and processing—not reversal of the original base fee or a guaranteed payment to every visitor.

### Which pending-transaction expenses can enter the Cashback audit?

A pending transaction with **no receipt** is not a gas expense actually paid to Ethereum for execution. A successful speed-up transaction **included on Ethereum Mainnet** can generate a receipt and may qualify if its gas was borne by the imported address and other conditions are met. A successful zero-value **cancellation** self-transfer can also consume network gas. A **reverted on-chain** transaction likewise has an actual receipt and fee. Eligibility is assessed under the current program rules; none of these receipts qualifies merely because the article mentions it.

The published program rules also state that qualifying activity **before importing the wallet** can count if it belongs to the same imported address and falls in the relevant 30-day window; fees **already reimbursed** through the program cannot be counted twice, and the public program has **no stated monetary cap**. The nominal amount of ETH or USDC transferred, price slippage, exchange service charges, Base fees and Arbitrum fees are not Ethereum Mainnet network gas paid by that address. Use real receipts rather than an app's fee estimate. <https://terenval.com/gas-fee-cashback/>

### Terenval Gas Recovery Eligibility Ledger — worked example

The following is a **hypothetical six-transaction audit**, not a record of an actual Terenval user. All receipts are assumed to belong to the **same imported Ethereum Mainnet sender** in the prior 30 days and none is previously reimbursed. The eligibility result remains subject to the actual program review.

| Hypothetical included receipt | Actual fee paid | Why it is a candidate |
| --- | ---: | --- |
| Ordinary ETH payment | 0.00042 ETH | Sender paid execution gas |
| ERC-20 token transfer | 0.00078 ETH | Sender paid Mainnet gas, not token amount |
| Successful DEX swap | 0.00370 ETH | Actual execution fee, not the quoted price impact |
| Reverted DEX swap | 0.00210 ETH | Execution failed, but on-chain gas was paid |
| Successful same-nonce cancellation | 0.00046 ETH | Self-transfer used gas even though ETH value was zero |
| Token approval | 0.00064 ETH | Included contract action with transaction fee |
| **Total potentially eligible gas** | **0.00810 ETH** | Only if all program conditions are met |
| **Illustrative 90% cashback request** | **0.00729 ETH** | Not an automatic or guaranteed payout |

Arithmetic: **0.00810 × 0.90 = 0.00729 ETH**. An on-chain payment to someone else, even $20,000 in token value, would **not** be part of the gas-fee numerator. A losing unconfirmed replacement candidate with no receipt would contribute **zero execution gas**. A Base transaction and a previously reimbursed Mainnet fee should be excluded. This method avoids the common mistake of counting **both** pending and winning same-nonce hashes as two network expenses.

### A practical 30-day address audit

1. Open the official [Cashback page](https://terenval.com/gas-fee-cashback/) and read the current published criteria; do not enter private keys on that public information page.
2. In a trusted Ethereum Mainnet explorer, find the imported **public address** and the transactions it **sent** over the previous 30 days.
3. Record each included transaction hash, date/time, `From`, status and **actual transaction fee in ETH**; distinguish execution fees from token values.
4. Exclude candidate records without included receipts, fees paid by someone else, other networks and any receipt already compensated.
5. Calculate 90% of the verified potentially eligible Mainnet fee sum for an **estimate**, not an entitlement or promised cash amount.
6. From the official Terenval Wallet on **Android**, import only an account you control using the wallet's documented procedure, then access the service request through the wallet. Protect the recovery phrase, verify the app and domain independently, and never share secrets with “cashback support.”
7. Retain the hashes and fee ledger for manual review and monitor the request through legitimate channels; **approval and payment are not guaranteed**.

### Does a failed transaction always qualify for 90% cashback?

Not necessarily. A failure that **never entered a block** has no Ethereum execution fee and therefore no paid gas to reimburse. A confirmed **reverted** transaction that used gas may be a candidate under the program's published inclusion of actually paid gas, but the address, timeframe, network, no-duplicate rules and any additional eligibility checks must still be satisfied. Always verify the current program terms before relying on a reimbursement in a spending decision.

### Why importing a wallet does not move historical fees or coins

Importing an existing compatible self-custody wallet into another wallet app normally exposes the **same on-chain address** to a second interface; it does not rewrite the blockchain's fee history and usually does not require a transfer of the assets. The old transactions remain attributable to their original sender. However, entering a recovery phrase into another application expands the number of environments in which those credentials are used. **Only import into software you have independently verified and understand**; for high-value keys, consider the security implications and available hardware-wallet compatibility. Terenval's offer should never be used as an excuse to disclose a seed phrase to an agent, website form or unsolicited message.

## Terenval Wallet Gas Sponsorship: When You Have Tokens but No ETH

The [Terenval Wallet Gas Sponsorship service](https://terenval.com/gas-sponsorship/) addresses an **access problem**, not a past-fee reimbursement. A user may hold USDC, USDT or another token on an imported Ethereum Mainnet address yet have insufficient ETH to pay for an ordinary on-chain action. Terenval publicly describes a pathway to **request** ETH for an ordinary operation with a small buffer, sent to the same qualifying imported Mainnet address. It is **not** a universal automated paymaster and does not guarantee a transaction will succeed or arrive at a certain time.

### Can sponsorship pay for a pending transaction's speed-up?

Do not assume it will. A request-based assistance service is not designed or advertised as an instantaneous guarantee to win a same-nonce replacement race. A user who urgently needs to replace a pending transaction should first establish whether the address is eligible, whether funding can arrive in time, and whether the original candidate may execute meanwhile. Sponsorship eligibility, amount and timing must be checked through the official wallet service. **Never send tokens to an intermediary who promises immediate priority inclusion in exchange for a fee.**

### Cashback and Sponsorship solve different problems

| User's actual problem | Relevant option | What it can address | What it cannot promise |
| --- | --- | --- | --- |
| Already paid qualifying Ethereum Mainnet gas within 30 days | Gas Fee Cashback | Request 90% of eligible fee expenses after wallet import and review | Reverse Ethereum execution or pay every fee automatically |
| Holds tokens on an imported Ethereum Mainnet address, but lacks ETH for normal gas | Wallet Gas Sponsorship | Request a limited gas-ETH assist for that address | Instant same-nonce replacement or unconditional funding |
| Wants future transactions to cost less | Fee estimation, timing, appropriate network/route | Potentially reduce new execution expense | Refund fees already consumed by Ethereum |
| Needs to stop a truly pending unauthorized operation | Security response and supported same-nonce replacement evaluation | Potentially replace an unconfirmed transaction | Recover a confirmed stolen payment or guarantee a win against an attacker |

A wallet address with **zero transaction history** or **no qualifying activity** should not be portrayed as assured of Cashback or Sponsorship. Read the current service requirements and independently confirm wallet compatibility and supported networks via [Terenval's official entry point](https://terenval.com/) and [supported networks information](https://wallet.terenval.com/info/supported-networks/).

## Terenval Evidence-before-Action Gate: When Not to Touch the Gas Settings

The **Evidence-before-Action Gate** is an editorial tool for deciding whether a proposed action is justified. It is deliberately designed to prevent panic-driven mistakes.

| Gate question | If **yes** | If **no** |
| --- | --- | --- |
| Do I control the sender account and the correct network? | Proceed to inspect nonce and status | Stop; an exchange or different network may be responsible |
| Is the original candidate verifiably *unconfirmed*? | Evaluate waiting or replacement | Examine receipt, app crediting or bridge state instead |
| Have I found the lowest unresolved nonce? | Address that nonce first | Do not attempt to accelerate only a later queued action |
| Is the original intended action still safe? | Speed-up may be rational if cost justifies it | Prefer careful cancellation evaluation or wait, not blind speed-up |
| Does the wallet actually support a trusted replacement flow? | Inspect and verify fee, nonce, recipient, calldata | Avoid improvised scripts or private-key websites |
| Can I afford the **actual likely fee** and the loss if the attempt fails? | Compare alternative options | Delay or seek legitimate support if available |
| Did a replacement actually gain a receipt? | Record winner and update ledger | Do not assume success; keep checking verified chain data |

**Author's position:** An extra fee is rational only when it solves the correct constraint **and** preserves the user's intended economic outcome. Paying to accelerate an already invalid swap is worse than tolerating a delay. Paying to cancel a payment that is already confirmed is impossible at the protocol level. Paying to “verify” a wallet with a seed phrase is not transaction recovery—it is a security incident.

## Six Practical Recovery Scenarios

These cases are illustrative, not reports of real network incidents. They show why an effective response changes with evidence.

### Scenario 1 — A simple ETH transfer has been pending for 35 minutes

The wallet shows a transaction hash on Ethereum Mainnet, Etherscan shows it unconfirmed, no earlier nonce is missing, and the desired payment is still correct. The user compares current fee conditions with the transaction's max fee and priority caps. They may wait or use the wallet's supported same-nonce speed-up if appropriate. They retain both hashes and check the winning receipt. They **do not create a new payment with nonce +1** merely to duplicate the original.

### Scenario 2 — A USDT transfer appears queued behind an old approval

The account's pending nonce is 18 for an approval; the USDT transfer has nonce 19. The user finds the earliest unresolved nonce 18 and investigates whether the approval should still execute. Replacing only nonce 19's fee cannot solve the nonce ordering constraint. If the approval remains risky, cancelling it safely may be preferable to speeding it up. The queued USDT transfer needs its own independent safety review once nonce 18 is resolved.

### Scenario 3 — The wallet says pending, but Etherscan cannot find the hash

The user verifies Ethereum Mainnet as the intended network and searches the sender address. They discover that a different same-nonce hash was included. The apparently missing transaction was replaced. The user reads the **winning hash**, not the stale local history, to determine whether money moved. If there is no included replacement, they check an independent provider and their wallet's broadcast state before doing anything irreversible.

### Scenario 4 — A DEX swap says failed and a fee was charged

The explorer shows block inclusion and receipt `status = 0`, with 175,000 hypothetical gas units used. There is nothing left to accelerate for that hash. The user inspects the contract error, swap deadline, token allowances and current market before retrying. The Ethereum fee is real; if paid by the imported Mainnet address within the relevant window, the receipt may be a **candidate** in a separate Terenval Cashback audit. It is not proof of an automatic refund.

### Scenario 5 — An exchange shows “processing” after the blockchain succeeded

The user sees a successful Ethereum receipt to the exchange's deposit address. The exchange's ledger has not credited the balance. The next step is to verify the exchange's token, network and confirmation policy and contact its authenticated support, not send another transfer. The transaction's gas cost is already historical; the off-chain credit is a separate problem.

### Scenario 6 — An Arbitrum withdrawal shows “waiting for finalization”

The outbound Arbitrum transaction is included, but the canonical L2-to-L1 withdrawal still awaits its protocol-defined message finalization and execution. The user tracks the official bridge state, understands the challenge period and checks any final claim/execute action. The extra delay is not necessarily an Ethereum Mainnet pending nonce problem. The user does not make a second withdrawal to “unlock” the first.

## How Much Is Speeding Up Worth? A Decision Model

A rational choice considers more than the delta between two gas quotes. Waiting can create economic exposure (for example, a time-sensitive liquidation or an expiring swap); speed-up can incur an incremental fee; cancellation can protect against an unwanted future execution but cannot guarantee it. The **Terenval Decision-Adjusted Transaction Cost** model is:

**Illustrative decision-adjusted cost = expected execution fee + externally attributable service costs + expected loss from delay or failed execution + security exposure.**

The last two terms are risk assessments, **not** objective on-chain prices. They must be made explicit instead of hidden inside a claim that higher fees are always justified.

### Three illustrative strategies

| Strategy | Hypothetical fee if included | Primary benefit | Main failure mode |
| --- | ---: | --- | --- |
| Wait for the original 21,000-gas transfer | 0.0004515 ETH under assumed future price | Avoid deliberate higher fee cap and new signing | Indeterminate wait; transaction may later execute unexpectedly |
| Speed up same payment | 0.0004830 ETH under assumed block conditions | Potentially improves inclusion competitiveness | Still no guarantee; could accelerate an unwanted payment |
| Cancel via same-nonce self-transfer | 0.0004830 ETH under assumed block conditions | May consume nonce without making original transfer | Original might execute first; included cancellation still costs gas |

The **incremental illustrative paid fee**, if the original would have executed in the same 20-gwei-base conditions, is **0.0000315 ETH** (0.0004830 minus 0.0004515), or about **$0.08** at the model's $2,500/ETH assumption. This comparison assumes each alternative could be executed in those particular hypothetical conditions. **It is not a forecast**, because in real life waiting changes the future base fee, probability of inclusion and potentially the application outcome.

### Why a $100 transaction can merit different urgency than a $100,000 transaction

Network gas often depends more on computation than transfer value. But *loss from an unwanted execution*, *opportunity cost from delay* and *exposure to fraud* may scale with value. For a large or security-sensitive action, a small incremental fee might be justified. For a non-urgent transfer, a large fee bump could be wasteful. No fixed “always bump by X% after Y minutes” rule captures the user's full risk.

## A Security Checklist for Transaction Recovery Scams

Criminals exploit the urgency of frozen-looking transfers. Warning signs include people offering a “validator unblock code,” a fee-reimbursement site that asks for your **seed phrase**, an instruction to move your whole balance to a “safe escrow” wallet, or a demand to sign unlimited token approvals before a pending transaction can be fixed. Such actions are not part of Ethereum's native pending-transaction process.

### What is safe to share during troubleshooting?

A **public transaction hash**, public blockchain address, network name and visible receipt/status are normally sufficient to investigate network mechanics, though they do expose transaction history and potentially sensitive financial associations. A recovery phrase, private key, wallet password, unpublished signed raw transaction and authentication token are not ordinary support evidence. For privacy, share the minimum public detail necessary.

### Verify the genuine wallet, explorer and service address

Open official sites from trusted bookmarks or independently typed domains. Use [Etherscan](https://etherscan.io/) for Ethereum Mainnet and [Terenval's official website](https://terenval.com/) for its services. A logo on a phishing page or a convincing AI-generated customer-support message does not establish authenticity. The [Terenval address-poisoning guide](https://wallet.terenval.com/answers/what-is-crypto-address-poisoning-and-how-to-avoid-it/) explains why a familiar-looking transaction history is not a reliable source for recipient addresses.

### If you suspect key compromise

Treat the matter as an incident involving ongoing signing authority. Never place additional funds into an address that an attacker may control just because it is short of gas. Consider whether approvals, delegated permissions and external software have exposed the account. Use independently verified security guidance and, when feasible, migrate *remaining* assets to a verified fresh address without disclosing keys. A same-nonce cancellation is not a general compromise-recovery guarantee.

## FAQ: Pending, Stuck, Failed and Replaced Ethereum Transactions

### 1. Why is my Ethereum transaction still pending?

The transaction has not yet been included in a block visible to the network you are checking. Common explanations include an insufficient max fee or priority fee, a lower unresolved sender nonce, limited propagation or a stale wallet display. Verify chain, hash, sender and nonce before altering any fee.

### 2. How long can an Ethereum transaction stay pending?

There is no guaranteed maximum waiting time for an individually submitted candidate. Inclusion depends on fee eligibility, network conditions, nonce ordering and propagation. A transaction may be included, replaced, dropped from some pools or rebroadcast later. Avoid relying on a fixed timeout to decide whether a second payment is safe.

### 3. How can I speed up a pending Ethereum transaction?

If the original is genuinely pending and you control the sender, a supported wallet may let you resubmit the intended action with **the same nonce** and more competitive fee parameters. Compare the submitted replacement with the original, keep both hashes and determine which one actually gets included. Not every wallet exposes this function.

### 4. Can I cancel an Ethereum transaction after sending it?

A transaction that is still unconfirmed can sometimes be replaced by a higher-fee transaction using the same account nonce, frequently a zero-value self-transfer. This is a **race** and not a guarantee. A successfully included Ethereum transaction cannot be retroactively cancelled using the same method.

### 5. Can I cancel a confirmed Ethereum transaction?

No. Once a transaction is included in canonical Ethereum history, its nonce is consumed and the executed state changes cannot simply be rolled back by sending another transaction. A subsequent transfer may reverse an economic position only if the receiving party or relevant smart contract permits it; that is different from cancellation.

### 6. Does speeding up mean I pay twice for gas?

Not for two alternative ordinary EOA transactions with the *same sender and nonce* on one canonical chain: only the included candidate consumes execution gas. The actual included replacement may cost more than the original would have cost. Separate approvals, retries with different nonces or other included actions can create additional expenses.

### 7. Why does my wallet show a huge maximum gas fee?

A maximum fee cap represents a spending ceiling under certain assumptions, not necessarily the confirmed charge. For ordinary EIP-1559 execution, read the included receipt's `gasUsed` and `effectiveGasPrice` to calculate actual gas paid. Avoid treating `gas limit × maxFeePerGas` as historical expenditure.

### 8. What is a nonce in an Ethereum transaction?

For a conventional Ethereum EOA, a nonce is the sender's sequential transaction counter. It prevents two ordinary transactions from consuming the same account sequence position on the canonical chain. Two signed candidates with the same sender and nonce compete to occupy that position, enabling typical speed-up or cancellation attempts.

### 9. What does “nonce too low” mean?

The nonce in a newly submitted candidate may already have been consumed by an included transaction. Check the sender's on-chain history for another hash at that nonce. Raising the fee on a candidate with a truly consumed nonce cannot make it execute again.

### 10. What does “replacement transaction underpriced” mean?

A node or provider may reject a new same-nonce candidate because its fee parameters do not satisfy the node's replacement policy. These policies vary. Geth documents a default 10% pool price-bump setting, but that is not a universal guarantee. Prefer the replacement procedure supported by your wallet and current network conditions.

### 11. Why is my new ETH transfer queued after another transaction?

The newer transaction may have a nonce higher than an unresolved earlier one. Conventional EOA transactions execute in nonce order. Inspect the lowest unresolved nonce first; paying more for a later queued action alone does not remove the earlier dependency.

### 12. Etherscan cannot find my transaction hash. Is it cancelled?

Not necessarily. The transaction might not have propagated widely, might belong to another chain, might have been replaced, or might be visible on a different provider. Verify the public sender account and exact network and check for an included same-nonce replacement. A missing hash is not sufficient evidence for another full outgoing payment.

### 13. What does “Dropped & Replaced” mean on Etherscan?

The original unconfirmed candidate is no longer the included outcome; a different transaction with the same sender and nonce has been accepted and confirmed. Inspect the **replacement hash and receipt** to determine whether the replacement executed the original payment, a self-transfer or another action.

### 14. Can a dropped Ethereum transaction come back?

Yes. Being removed from a particular node's transaction pool is not an on-chain terminal state. Another node may still hold the signed transaction, which can be rebroadcast while valid. This is why users should not equate “dropped” with a permanent cancellation of an unconfirmed transfer.

### 15. Is a pending transaction charging gas every minute?

No. Ordinary Ethereum execution gas is not a clock-based meter that accumulates fees every minute a transaction sits in a pool. A confirmed included execution creates the actual fee; other separate application or off-chain service charges may have their own rules. The pending wallet quote is not a recurring on-chain deduction.

### 16. Why did I pay gas for a failed Ethereum transaction?

If the transaction was included but its contract execution reverted or ran out of gas, the network still performed computation. Its actual gas is recorded in the receipt. A transaction rejected before inclusion is a different case and does not have an execution receipt. Check the transaction status and block number first.

### 17. Can I recover the gas from a failed swap?

Ethereum itself does not reverse an executed fee because the swap reverted. A separate program may offer a conditional reimbursement. Under its published terms, Terenval Gas Fee Cashback permits requests for 90% of eligible, actually paid Ethereum Mainnet gas during the prior 30 days for a qualifying imported address; approval is not automatic.

### 18. Does paying more gas make a failed swap succeed?

Not necessarily. More competitive fee parameters may make a transaction *more likely to be included sooner*, but cannot solve an invalid contract condition, missing approval, slippage requirement or expired deadline. A second attempt could fail again and consume more gas. Diagnose the original receipt before retrying.

### 19. Why is my USDC transfer pending?

First check whether the USDC transfer is on Ethereum Mainnet or another network, the exact token contract, the sender's nonce and ETH available for gas. A transfer may remain unconfirmed, be queued behind an earlier nonce or be completed but absent from the wallet display. Use the correct chain explorer.

### 20. Why is my USDT transfer stuck on Ethereum?

USDT on Ethereum is a token contract interaction. Its pending state can result from gas pricing, nonce ordering or broadcasting. If included, inspect the token transfer events and actual receipt. Avoid sending a second USDT transfer just because a wallet has not updated its UI.

### 21. My transaction is confirmed but the exchange has not credited me. Why?

Exchanges can require their own confirmation thresholds and compliance or ledger checks. Verify the destination address, token contract, chain and receipt, and then contact the exchange's authenticated support. A newly signed transaction from your personal wallet does not fix an exchange's off-chain crediting workflow.

### 22. Why is my Arbitrum or Base transaction not visible on Ethereum Mainnet?

They are separate networks with different explorers and transaction histories. A hash shown on Arbitrum or Base must be checked against that network's records. Bridging can create distinct origin and destination operations that need separate tracking, and Ethereum Mainnet gas caps do not directly describe L2 execution fees.

### 23. Why does an Arbitrum withdrawal take several days?

A canonical optimistic-rollup L2-to-L1 withdrawal has a challenge and finalization process that differs from an ordinary L2 transaction. Current Arbitrum documentation describes an approximately 6.4-day period for canonical withdrawal processing and later execution. Verify the official bridge's message status rather than resending tokens.

### 24. Can I cancel a pending transaction sent from an exchange account?

Ordinarily, the account that signs and broadcasts the on-chain withdrawal is controlled by the exchange. A recipient who does not control that sender cannot issue its replacement transaction. Check the exchange's authenticated withdrawal page and support process instead of changing your personal wallet's nonce.

### 25. How do I know whether my transaction was actually cancelled?

Find a confirmed same-sender, same-nonce **replacement receipt**, such as a zero-value self-transfer, and verify that the original action was not included first. A “Cancel submitted” toast is only evidence of attempting the replacement, not proof that the original cannot be included.

### 26. Does Terenval Wallet have a built-in transaction speed-up button?

This guide does **not** claim that Terenval Wallet currently implements a native speed-up, cancellation button or custom nonce editor. Check the actual supported wallet version and documentation before assuming a control exists. The general recovery mechanics here are educational, not a feature announcement.

### 27. Can I request Terenval cashback on a transaction from before importing my wallet?

Terenval's published Gas Fee Cashback terms say qualifying Ethereum Mainnet fees **from the same imported address** in the preceding 30 days can count even when the transactions occurred before import. Eligibility, actual fees, no prior reimbursement and the service's other conditions still apply. Importing does not rewrite blockchain history.

### 28. Do unconfirmed or replaced transaction hashes count for cashback?

An unconfirmed, non-included candidate has no executed Ethereum gas receipt, so it supplies no past execution fee. Count the **included winning replacement** or any other confirmed gas-consuming Mainnet transaction that meets the published terms. Do not count two alternative same-nonce hashes as two execution expenses.

### 29. Can Terenval Wallet Gas Sponsorship fund an address with tokens but no ETH?

Terenval describes a request service for qualifying imported Ethereum Mainnet accounts that already hold tokens but lack gas ETH for an ordinary transaction. It is a discretionary request path, not a guaranteed or instantaneous transfer. It should not be described as automatic Ethereum gas sponsorship or a reliable way to win an urgent cancellation race.

### 30. What is the safest first step when a crypto transfer appears stuck?

Verify the **network**, **public hash**, **sender**, **nonce** and **on-chain receipt status** using reliable tools. Do not sign a second full payment, use a seed-phrase “recovery” site or pay a stranger to free a transaction before checking these facts. If the chain action is complete, address the separate application or exchange workflow instead.

## Practical Checklist: Before and After a Replacement

### Before signing

- Match **network, sender, recipient, token contract and nonce** to the exact original action.
- Check a trustworthy explorer and distinguish an included receipt from an unconfirmed candidate.
- Find the **lowest unresolved sender nonce**, not just the transaction with the largest balance impact.
- Decide whether the intended operation remains safe: a swap, approval or transfer may now be undesirable.
- Use only documented wallet controls; review the fee cap and priority fee before accepting them.
- Keep private keys, seed phrases and raw signing material away from support chats and repair websites.

### After signing or waiting

- Record the new hash and continue checking the original hash until one is included or conditions change.
- Examine the **winning receipt**, including sender, nonce, success/revert status, gas used, effective price and token events.
- Confirm the **actual destination balance or service settlement**, not just the wallet's submission notification.
- If reviewing historical gas expenses, count only **included fees actually paid on the appropriate network**.
- For eligible Terenval users, consult the current [Cashback](https://terenval.com/gas-fee-cashback/) or [Sponsorship](https://terenval.com/gas-sponsorship/) conditions through the authenticated wallet workflow.

## Related Terenval Guides and Services

| Topic | Recommended resource | Why it is related |
| --- | --- | --- |
| Calculate gas, EIP-1559 and fee receipts | [What Are Gas Fees in Crypto?](https://wallet.terenval.com/answers/what-are-gas-fees-in-crypto/) | Understand base fee, tip, gas used and actual cost |
| Avoid loss in swaps | [What Is Slippage in Crypto?](https://wallet.terenval.com/answers/what-is-slippage-in-crypto/) | A pending swap can become unfavorable or revert |
| Understand L1/L2 costs | [Ethereum Layer 2 Networks and Gas Fees](https://wallet.terenval.com/answers/ethereum-layer-2-networks-and-gas-fees/) | Ethereum, Base and Arbitrum have distinct fee contexts |
| Track transfers across networks | [What Is a Crypto Bridge?](https://wallet.terenval.com/answers/what-is-a-crypto-bridge/) | A destination-chain delay is not necessarily a pending Ethereum transaction |
| Avoid dangerous token permissions | [How to Check and Revoke Token Approvals](https://wallet.terenval.com/answers/how-to-check-and-revoke-token-approvals-in-a-crypto-wallet/) | Pending approvals and existing allowances create different risks |
| Keep recovery practices safe | [Crypto Address Poisoning](https://wallet.terenval.com/answers/what-is-crypto-address-poisoning-and-how-to-avoid-it/) | Do not copy destinations from suspicious transaction history |
| Request eligible historical Mainnet gas reimbursement | [Terenval Gas Fee Cashback](https://terenval.com/gas-fee-cashback/) | Separate application for qualifying *already-paid* gas |
| Request gas help when imported tokens are stranded | [Terenval Wallet Gas Sponsorship](https://terenval.com/gas-sponsorship/) | Separate application for eligible imported Mainnet addresses lacking ETH |

## Sources and Verification Method

The technical explanation is based primarily on the following authoritative materials; their links are also preserved in the YAML `sources` field for the Terenval Publisher. Technical behavior and Terenval commercial conditions are kept separate.

- [Ethereum.org: transaction data and lifecycle](https://ethereum.org/developers/docs/transactions/) — hashes, nonces, pool, inclusion and finalization.
- [Ethereum.org: gas fees](https://ethereum.org/developers/docs/gas/) and [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) — gas used, fee caps, base fee, priority fee and execution.
- [Ethereum.org: JSON-RPC](https://ethereum.org/developers/docs/apis/json-rpc/) and [EIP-1474](https://eips.ethereum.org/EIPS/eip-1474) — transaction count, pending status and receipt evidence.
- [Geth transaction pool](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-txpool) and [Geth options](https://geth.ethereum.org/docs/fundamentals/command-line-options) — node-dependent pending/queued pool behavior and price-bump configuration.
- [MetaMask: speed up or cancel](https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction), [nonce customization](https://support.metamask.io/configure/transactions/how-to-customize-a-transaction-nonce), and [pending replacement troubleshooting](https://support.metamask.io/manage-crypto/transactions/why-cant-i-replace-a-pending-transaction-/) — concrete examples from one wallet provider, not general proof of another wallet's features.
- [Etherscan: dropped and replaced](https://info.etherscan.com/transaction-dropped-replaced/) — explorer interpretation of unconfirmed candidates.
- [Arbitrum: network and withdrawal FAQ](https://docs.arbitrum.io/get-started/arbitrum-introduction) and [L2-to-L1 messaging](https://docs.arbitrum.io/how-arbitrum-works/deep-dives/l2-to-l1-messaging) — why bridge completion differs from ordinary transaction inclusion.
- [Terenval Gas Fee Cashback](https://terenval.com/gas-fee-cashback/) and [Terenval Gas Sponsorship](https://terenval.com/gas-sponsorship/) — first-party statements of currently advertised services, **not** independent evidence of claims approval or speed.

## Editorial Context, Limitations and Disclosure

**Who prepared this guide.** This material was prepared by the **Terenval Editorial Team**. It combines Ethereum protocol documentation, public help-center guidance, source-attributed service rules and original editorial decision frameworks. The case studies, cost models and ledgers are **original educational illustrations** intended to make transaction evidence and the consequences of user decisions testable. They are not measurements of Ethereum's average current fee, the probability of an individual transaction's inclusion or the likelihood of Terenval paying a particular claim.

**Why our perspective differs from a generic troubleshooting article.** A large share of popular advice begins with “increase gas,” despite the possibility that the user has a missing nonce, a stale RPC, a completed but reverted execution, an exchange ledger delay or a bridge challenge period. Our central recommendation is to **classify the evidence before spending more money**, record the winning receipt rather than a wallet estimate, and separate the original transaction outcome from any subsequent cashback or assistance request. This is an editorial method for reducing avoidable operational errors, not a proprietary network protocol.

**Commercial relationship.** Terenval Wallet, Gas Fee Cashback and Gas Sponsorship are products and services of the same ecosystem responsible for publishing this guide. Links to Terenval products constitute native, clearly attributable promotion. Their first-party pages describe offered conditions; they do not independently validate claims approval, eligibility in every case, reimbursement speed, or a guarantee of execution. This article does **not** claim that Terenval Wallet has a native nonce editor, automated cancel or speed-up workflow, paymaster, cross-chain rescue function or on-chain refund feature unless separately documented and verified.

**Information limits.** Network congestion, client txpool policy, EVM semantics, wallet interfaces, specific L2 bridges, token contracts and service terms can change. Information was reviewed with a **November 11, 2026 cutoff**. Any number in a model is hypothetical unless a cited source identifies it as protocol documentation. In particular, there is **no guaranteed cheapest gas hour, fixed pending timeout or guaranteed replacement fee bump**. Before initiating any financial action, check current independent chain evidence and current official product conditions.

**Safety and scope.** This guide is not individual financial, legal, security-incident, tax or investment advice. A private key or recovery phrase is not needed to inspect a public transaction. Never entrust one to strangers offering to release funds, and consider expert support where a potentially compromised high-value wallet or complex contract is involved. The most reliable first step is often the simplest: **verify exactly what the blockchain did—and did not do—before signing anything else.**

## Editorial & technical review

- Published by: Terenval
- Technical review: Terenval Wallet team
- Last reviewed: 2026-11-11

## Sources

- [Ethereum.org — Transactions and Transaction Lifecycle](https://ethereum.org/developers/docs/transactions/)
- [Ethereum.org — Ethereum Gas and Fees](https://ethereum.org/developers/docs/gas/)
- [Ethereum.org — JSON-RPC API Reference](https://ethereum.org/developers/docs/apis/json-rpc/)
- [Ethereum.org — Frequently Asked Questions, Pending Transactions](https://ethereum.org/community/support/faq/)
- [Ethereum Improvement Proposal — EIP-1559 Fee Market Change](https://eips.ethereum.org/EIPS/eip-1559)
- [Ethereum Improvement Proposal — EIP-1474 Remote Procedure Call Specification](https://eips.ethereum.org/EIPS/eip-1474)
- [Go-Ethereum — Transaction Pool Inspection](https://geth.ethereum.org/docs/interacting-with-geth/rpc/ns-txpool)
- [Go-Ethereum — Command-Line Transaction Pool Price Bump Setting](https://geth.ethereum.org/docs/fundamentals/command-line-options)
- [MetaMask Help Center — Speed Up or Cancel a Pending Transaction](https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction)
- [MetaMask Help Center — Why Can't I Replace a Pending Transaction?](https://support.metamask.io/manage-crypto/transactions/why-cant-i-replace-a-pending-transaction-/)
- [MetaMask Help Center — How to Customize a Transaction Nonce](https://support.metamask.io/configure/transactions/how-to-customize-a-transaction-nonce)
- [Etherscan — Transaction Dropped and Replaced](https://info.etherscan.com/transaction-dropped-replaced/)
- [Etherscan — Ethereum Block Explorer](https://etherscan.io/)
- [Arbitrum Documentation — Withdrawal Delay and Confirmation](https://docs.arbitrum.io/get-started/arbitrum-introduction)
- [Arbitrum Documentation — L2 to L1 Message Lifecycle](https://docs.arbitrum.io/how-arbitrum-works/deep-dives/l2-to-l1-messaging)
- [ERC-4337 — Account Abstraction and User Operations](https://ercs.ethereum.org/ERCS/erc-4337)
- [Terenval — Ethereum Gas Fee Cashback, Published Program Terms](https://terenval.com/gas-fee-cashback/)
- [Terenval — Wallet Gas Sponsorship, Published Service Description](https://terenval.com/gas-sponsorship/)
- [Terenval — Wallet and Official Entry Point](https://terenval.com/)
- [Terenval — Supported Networks](https://wallet.terenval.com/info/supported-networks/)
- [Terenval — Ethereum Gas Fees and How to Pay Less](https://wallet.terenval.com/answers/what-are-gas-fees-in-crypto/)

Official article: https://wallet.terenval.com/answers/why-is-my-ethereum-transaction-pending/

[Machine-oriented Terenval index](https://wallet.terenval.com/llms.txt)
