Layer 2 networks can make routine transactions cheaper, but moving funds to one has costs and risks of its own. For transactions on Ethereum Mainnet, check current fees, review your wallet’s estimate and consider waiting if the transaction is not urgent. Before a contract interaction, check its details and simulate it when possible. We’ll cover those habits and what to check when a transaction remains pending.
TL;DR:
- A reverted transaction still consumes gas, so simulate unfamiliar contract calls and check allowances or slippage; raising the priority fee cannot repair incorrect inputs.
- Before bridging, compare the costs with potential savings across planned transactions, check the token on the destination network, and allow for possible withdrawal delays.
- For a transaction that can wait, check a current gas estimate rather than relying on a fixed time of day or a weekend discount.
- To attempt to speed up a pending transaction, use the same nonce with sufficiently competitive fee settings; a later nonce may remain queued behind it.
Table of Contents
- How Ethereum gas actually works
- Everyday tactics that save the most fees for typical users
- Layer 2s, rollups, and bridging: what to check before you move funds
- Timing and gas trackers: rules of thumb that actually hold up
- Avoiding failed transactions and fixing a stuck one
- Advanced tactics for power users and developers
- A practical checklist before you hit confirm
- A guided path if you’d rather not figure this out alone
- FAQ
- Sources
How Ethereum gas actually works
For an included Ethereum transaction, the fee is the gas used multiplied by the effective price per gas: the base fee plus the priority fee, as explained by Ethereum. The protocol sets the base fee, which is burned. The priority fee goes to the validator. Where a wallet exposes both settings, the maximum priority fee limits the tip, while maxFeePerGas caps the total price per gas unit; the cap must be high enough to cover the base fee for inclusion.
Here’s the part that trips people up: a contract call that is included on-chain but reverts still uses gas, even though its intended action fails. Bad parameters, insufficient allowance or a breached slippage limit can cause a revert. A transaction rejected before inclusion is different. Raising the priority fee cannot correct bad inputs; reviewing them and simulating the call when possible can help identify errors, though a simulation cannot guarantee success when conditions change.
Everyday tactics that save the most fees for typical users
Most of your savings come from a handful of habits, not clever tricks.
- Compare Mainnet with an Ethereum rollup for the transaction you need. Rollups execute transactions on Layer 2 and settle on Ethereum; they do not eliminate reliance on Mainnet. Check application availability, fees, bridge risks and withdrawal timing before choosing a network.
- Check a gas tracker before submitting anything non-urgent, and treat suggested gwei numbers as a starting point, not a floor.
- If your wallet offers advanced fee controls, compare its suggested maximum priority fee and total fee cap with current conditions; a lower tip may save money but delay inclusion.
- Where supported, batching may share transaction overhead across actions. Extra execution and data still consume gas, so compare estimated totals before choosing it.
- Favor dApps with gas-optimized contract design, since some protocols spend noticeably less gas per interaction than others doing the same job.
Before confirming: Review the wallet’s estimated total fee and the transaction details. A contract interaction can use more gas than a simple transfer; its total estimate cannot be compared directly with a tracker’s base fee per gas unit. Check separately whether the dApp asks for a token approval.
Advanced wallet controls may let you set a maximum priority fee and a maximum total fee per gas unit. A lower tip might reduce the cost of a transaction that can wait, but it can also cause a long delay or prevent inclusion under current conditions. Check the live estimate and your deadline before changing the settings.
Layer 2s, rollups, and bridging: what to check before you move funds
Rollups process transactions off Ethereum Mainnet and publish data to it, spreading some costs across many users. Fees still vary by network and transaction. Optimistic rollups allow a challenge period, so a standard withdrawal to Mainnet can take days; faster routes may charge additional fees. ZK-rollups use validity proofs, but withdrawal timing still depends on the network and proof verification.
The Dencun upgrade introduced blobs, which can reduce the cost of publishing rollup data to Ethereum. What a user pays still depends on the network and conditions. Before bridging funds, run through a short checklist:
- Confirm the bridge fee and compare it against what you’d save over several transactions, not just one.
- Check that the token you’re moving is actually usable on the destination L2 without a second swap.
- Note the withdrawal delay back to Mainnet, especially on optimistic rollups, since it can run to days.
- Review the bridge contract’s track record before trusting it with a meaningful amount.
Our bridge risk guide walks through these checks in more depth if you’re moving a larger position.
Timing and gas trackers: rules of thumb that actually hold up
Gas prices change with network demand, but a fixed clock or weekend rule cannot tell you what the next transaction will cost.
- For a transaction that can wait, check a live gas tracker alongside your wallet’s estimated total fee.
- If the current cost is too high for your purpose, wait and check again rather than assuming a particular hour will be cheaper.
- If a tracker or wallet offers a fee alert, you can use it to monitor a price you would consider acceptable.
- For an urgent transaction, weigh the current estimate against the risk that waiting will miss your deadline.
Check the estimate again just before confirming: conditions can change while you wait.
Avoiding failed transactions and fixing a stuck one
A transaction that reverts on-chain differs from one that is still pending. For a revert, inspect the contract inputs, allowance and slippage conditions. Raising the priority fee will not repair those errors. A supported simulation can help identify problems before submission, but conditions may change before inclusion.
A pending transaction has not yet been included; its fee settings or other conditions may be responsible. MetaMask’s support documentation explains how to attempt a same-nonce replacement while the original remains pending.
- To attempt to speed it up, use your wallet’s speed-up option or submit a replacement with the same nonce and sufficiently competitive fee settings.
- To attempt to cancel it, submit a zero-ETH transfer to yourself with the same nonce and sufficiently competitive fee settings. Cancellation is not guaranteed, and a confirmed transaction cannot be reversed this way.
Pro Tip: Never send a new transaction with a higher nonce while an earlier one is still stuck. Ethereum processes nonces in order, so the new one will just wait behind the old one instead of fixing anything.
Advanced tactics for power users and developers
For frequent users and developers, contract-level batching may share fixed transaction overhead across several actions, though execution and data costs remain. Compact encoding can reduce calldata costs where the contract design permits it; compare the total estimated gas for the alternatives.
Where a token and application support permit (EIP-2612), a signed message may replace a separate on-chain approval transaction. The resulting interaction still costs gas. Older gas-token schemes relied on refunds whose usefulness was substantially reduced by EIP-3529; they are not a substitute for comparing today’s transaction costs.
A practical checklist before you hit confirm
Before confirming, ask whether the transaction can happen on an L2 and whether getting there is worth the bridge costs and risks. For Mainnet, compare a live tracker with your wallet’s estimated total fee. Review fee settings rather than lowering the tip by default; check contract inputs and simulate unfamiliar calls where supported; verify whether a separate approval is needed. If an earlier transaction is pending, check its nonce before submitting another. Our risk management guide offers broader context for decisions beyond simple transfers.
A guided path if you’d rather not figure this out alone
Gas fees are one cost to consider when assessing whether a crypto position should remain idle or be used in DeFi. The potential income also needs to be weighed against transaction costs and the risk of loss. OverseasDeFi offers portfolio tools, a portfolio-aware AI coach and human guidance to help holders frame those questions. Community and Accelerator provide different levels of learning and support; check the current offerings for details. The decisions remain yours.
If you want to see how this fits into a broader income strategy, start with our guide to estimating income from BTC and ETH, or visit OverseasDeFi to see which plan fits where you are.
FAQ
What are gas fees in cryptocurrency?
Gas fees are the payments users make to have their transactions processed on a blockchain like Ethereum, calculated as gas used times the combined base fee and priority fee, per ethereum.org. The base fee is burned and the priority fee goes to the validator who includes your transaction.
Do failed Ethereum transactions cost gas?
An included transaction that reverts on-chain still consumes gas. A transaction rejected before it is included is different and may incur no on-chain fee. Check the transaction status before deciding what to fix.
When might bridging cost more than it saves?
If you expect only one or two transactions on the destination network, the bridge and eventual withdrawal costs may outweigh the lower transaction fees. Compare the estimated cost of your planned transactions on both networks, including any withdrawal or swap, before moving funds.
Sources
- Ethereum
- Dencun mainnet announcement | Ethereum Blog
- How to speed up or cancel a pending transaction | MetaMask Support