Ethereum Gas Fees: Base Fee, Tip, and Blob Gas

Every action on Ethereum costs something, and that cost is called a gas fee. Gas fees are the payment required to get work done on the Ethereum network. "Gas" is the unit used to measure computation and other network resources; the fee itself is paid in ether (ETH), Ethereum's native asset. A transaction costs more when it uses more gas, or when the cost per unit of gas rises.

The formula is simple: gas fee equals gas used multiplied by cost per unit of gas. For an ordinary Ethereum transaction, that cost per unit is made up of two parts — the base fee and the priority fee. The base fee is set by the protocol and required for inclusion; the priority fee is an extra amount senders add to make their transaction more attractive to validators, the network participants who add blocks to the chain.

A gas limit is different from gas used. The gas limit is the maximum amount of ordinary execution gas a sender allows a transaction to consume; gas used is what the transaction actually spends during execution. Setting a higher gas limit doesn't automatically raise the final fee — the actual charge depends on what the transaction consumes and on fee conditions at the moment it's included in a block.

1. A wallet creates a transaction — a simple ETH transfer, or a smart-contract call, which is a request to execute code stored on Ethereum.

2. The wallet estimates gas. For contract interactions, the wallet or a connected service may simulate the call to estimate how much ordinary gas it will need. That estimate is useful, but it's not a guarantee — blockchain state can change before the transaction is actually included.

3. The sender sets fee parameters and signs. The transaction carries a gas limit and fee settings, and the sender authorizes it with a private key.

4. The transaction is broadcast to Ethereum nodes. Nodes check whether it's valid and whether the sender can cover the maximum potential charge. Valid transactions may then wait in a pending pool.

5. A validator includes the transaction in a block. The priority fee makes a transaction more attractive for inclusion, but it doesn't guarantee any specific confirmation time.

6. The Ethereum Virtual Machine (EVM), the software environment that runs Ethereum's code, executes the transaction. Gas is consumed as execution proceeds, in proportion to the work done.

7. The protocol applies the fee split. The base fee is burned — removed from circulation entirely — and the priority fee goes to the validator that included the transaction.

Picture the gas limit as a ceiling and gas used as the work that actually happened underneath it. The ceiling matters, but it isn't the bill.

The same fee logic applies across common Ethereum actions: sending ETH, transferring tokens, approving a token allowance, swapping assets on a decentralized exchange, and interacting with lending or bridging contracts. These actions can use very different amounts of gas, because each one triggers different code paths and storage changes.

Ethereum also has a separate fee type for blob-carrying transactions, introduced under EIP-4844, titled "Shard Blob Transactions." Blob gas is distinct from ordinary execution gas and carries its own base fee. EIP-4844 was designed for blob data used in contexts such as rollup data publication.

For blob-carrying transactions, ordinary execution gas and blob gas cover different resources, so a single transaction can carry both an execution fee and a blob-related fee.

Ethereum fees move with network demand. Because the base fee responds to demand from the prior block, a wallet's fee estimate can go stale between the moment it's displayed and the moment the transaction is actually included. Two transactions that look similar can still cost different amounts, if they run different code paths or land under different network conditions.

A failed transaction can still cost gas. If a smart-contract call reverts or runs out of gas, the intended state change may never happen — but the network already performed the computation and verified it. That work doesn't come free just because it didn't succeed.

EIP-4844 adds a separate limitation on top of that: blob fees are deducted before execution and are not refunded if execution fails. A blob transaction can therefore carry cost in both its execution and blob components, regardless of outcome.

Wallets and apps don't label these parts consistently. One interface may show a single "network fee," while another breaks out a maximum fee, a priority fee, or a blob fee separately. The labels aren't standardized across products.

This article doesn't provide a live gas quote, tax guidance, or rules for other blockchains. The sources behind this piece also don't include a documented real-world failed-transaction incident, so the explanation above covers how failure behaves mechanically rather than pointing to a named historical case.

No verified documentation about Assetara's supported networks, custody model, transaction flow, or fee schedule was available for this piece. So no Assetara-specific claim is made here about whether Assetara supports Ethereum transactions, displays a particular fee field, or passes network fees through at cost.

The useful takeaway is narrower: if an Assetara product surfaces an Ethereum transaction, the network fee and any Assetara platform charge are separate things, unless product documentation explicitly says otherwise. Readers should rely on the fee disclosure shown for the specific action they're taking, and on Assetara's current official documentation.

The base fee is the protocol-set minimum, per unit of gas, required for inclusion — and it's burned. The priority fee is an extra amount paid to the validator that includes the transaction.

Because Ethereum may have already done computation before the failure occurred. If a contract call reverts or runs out of gas, the state change won't complete, but the gas already consumed during the attempt can still be charged.

No. Blob gas is a separate gas type introduced by EIP-4844 with its own base fee. Ordinary gas covers execution in Ethereum's execution environment.

No. A wallet can estimate and cap fees, but network demand and blockchain state can shift before inclusion — and a transaction can still fail after already using gas.

Not by itself. The gas limit mainly sets a ceiling on ordinary execution gas. Inclusion depends more directly on the effective fee per unit of gas and on current block capacity.