Skip to content
Financial Context Wiki

Ethereum Priority Fee

A practical guide to Ethereum EIP-1559 priority fees, fee caps, effective gas price, inclusion incentives, estimation, replacement and receipt reconciliation.

Updated

For educational purposes only; not transaction, security or investment advice. Fees and inclusion depend on the exact chain, transaction type, block conditions, wallet, RPC, relay, builder and validator behavior.

Direct answer

On Ethereum, a priority fee, or tip, is the execution-gas amount per unit that remains for the block’s fee recipient after the protocol burns the base fee. In a type-2 EIP-1559 transaction, maxPriorityFeePerGas is only a cap: the realized priority fee per gas is min(maxPriorityFeePerGas, maxFeePerGas - baseFeePerGas), and the effective gas price is the base fee plus that realized priority fee.

A larger competitive tip can improve the chance of timely inclusion, but it does not guarantee the next block, a particular ordering or successful execution. The transaction must still be valid, its total fee cap must cover the inclusion block’s base fee, and builders or validators may consider private order flow, bundles, MEV, local policy and other constraints. Terminology and fee rules differ on other chains and L2s, so do not transplant Ethereum’s formula without checking that network.

Network fee
0.000462 native
Fiat equivalent
$1.39
Base fee
22 gwei

Outputs are educational approximations. They exclude venue rules, taxes, latency, oracle behavior, and other protocol-specific parameters unless shown.

How it works

  1. Pin the chain, transaction type, sender, nonce, intended calldata, gas limit, current head and submission route. Type-2 transactions expose maxPriorityFeePerGas and maxFeePerGas; legacy transactions expose one gasPrice, whose amount above the base fee becomes the effective priority portion when included after EIP-1559.
  2. Estimate conditions rather than copying one static tip. A wallet or RPC can use recent blocks, pending demand and eth_feeHistory; its reward percentiles describe historical effective priority fees weighted by gas used, not a promise for the next block.
  3. Set two distinct caps. maxPriorityFeePerGas limits the requested tip, while maxFeePerGas limits base fee plus tip. Unused gas and unused cap headroom are not charged merely because the caps were authorized.
  4. At a candidate block, require maxFeePerGas >= baseFeePerGas. Then calculate effectivePriorityFeePerGas = min(maxPriorityFeePerGas, maxFeePerGas - baseFeePerGas) and effectiveGasPrice = baseFeePerGas + effectivePriorityFeePerGas.
  5. Treat the tip as an inclusion incentive, not an ordering contract. A block builder can optimize total block value, bundles and validity constraints rather than sort every public transaction by tip; a zero or low tip may still be included, while a high tip may still wait or fail.
  6. After inclusion, reconcile the receipt and block. Record gasUsed, receipt effectiveGasPrice, block baseFeePerGas, status, block hash and confirmation depth. Derive the execution fee as gasUsed * effectiveGasPrice and the priority portion as gasUsed * (effectiveGasPrice - baseFeePerGas).
  7. If a transaction remains pending, reassess the base-fee ceiling and route before replacing it. Same-sender, same-nonce replacement is client and pool policy, often requires bumps to multiple fee fields, and creates a race; a wallet’s Cancel action cannot reverse a transaction already included.

Worked examples

  • Tip below both caps. Gas used is 70,000, base fee is 25 gwei, max priority fee is 3 gwei, and max fee is 40 gwei. The realized priority fee is min(3, 40 - 25) = 3 gwei; effective gas price is 28 gwei. The execution fee is 70,000 * 28 gwei = 0.001960 ETH, split into 0.001750 ETH burned and 0.000210 ETH credited as the priority portion.
  • Total cap binds. Keep caps at 3/40 gwei, but let the inclusion-block base fee reach 38 gwei. The realized priority fee falls to min(3, 40 - 38) = 2 gwei, so effective gas price is 40 gwei. At a 41 gwei base fee, the transaction cannot be included under that 40 gwei max fee even though its requested tip is high.
  • Estimate is not a guarantee. If recent eth_feeHistory percentiles suggest 2 gwei, that observation is a starting point. A sudden burst of demand, a private bundle, an RPC’s limited view or a builder’s policy can change inclusion outcomes; verify the actual receipt instead of treating the estimate as a service-level promise.

Risks

  • Using the wrong chain, fee token, transaction type or units such as wei, gwei and ETH.
  • Treating maxPriorityFeePerGas as the amount necessarily paid.
  • Forgetting that a rising base fee can squeeze the realized tip or make the transaction ineligible under maxFeePerGas.
  • Assuming the highest visible tip guarantees first position or next-block inclusion.
  • Relying on stale wallet, RPC or fee-history estimates during rapidly changing demand.
  • Overpaying because the wallet exposes aggressive defaults or because caps are confused with actual cost.
  • Believing a high tip repairs invalid calldata, insufficient gas, a revert, an expired deadline or a malicious contract.
  • Ignoring private relays, bundles, MEV, censorship and builder or validator policy.
  • Replacing the wrong nonce, failing a pool’s bump rule or sending conflicting value-bearing transactions.
  • Reading a pending label as global truth, or treating one confirmation as finality.
  • Applying Ethereum’s execution-tip formula to an L2 or another chain with different fee components and recipients.

Common misconceptions

  • The max priority fee is always paid. It is a cap; the total fee cap can reduce the realized tip.
  • A higher tip guarantees success. It may improve inclusion competitiveness but cannot guarantee ordering, execution success or finality.
  • The max fee is an extra charge on top of base fee and tip. It is the ceiling that covers both for type-2 execution gas.
  • Unused gas or fee-cap headroom is spent. Actual execution charges use receipt gas used and effective gas price.
  • Every network uses Ethereum’s priority-fee mechanics. L2s and other chains can have additional or different fee markets, sequencer policies and recipients.

Sources

Navigation

Search the wiki...