Ethereum execution gas and blob gas price different resources. An ordinary L1 transfer pays for its execution; a blob-carrying transaction also pays for the blob data it publishes. A rollup user usually sees a further accounting layer: the L2 charges its own transaction fee, which can include a share or estimate of L1 data costs. The whole blob transaction’s cost is not automatically your personal transfer fee.
Follow who submitted which transaction
First identify the network of the transaction in your wallet. An Ethereum-mainnet transfer, an L2 user transaction and the batch publication on Ethereum are not the same transaction merely because ETH appears in all three descriptions. Each has its own sender, record and purpose. A mainnet gas dashboard cannot, by itself, explain the final amount charged for an L2 interaction.
The Ethereum transaction guide distinguishes blob-carrying transactions from other transaction types. These are used to publish blob data, notably for rollups. You do not turn a normal ETH payment into a lower-cost blob payment by selecting a different price unit in a wallet. Check the operation you actually intend to perform rather than treating ‘blob’ as a discount switch.
| Record you are reading | What is being paid for | Who submits that operation | Wrong comparison |
|---|---|---|---|
| Ordinary L1 transfer receipt | Execution of that Ethereum transaction | The L1 transaction sender | Replacing its execution price with a blob price |
| Blob-carrying L1 transaction | Execution plus publication of its blob data | The sender of the blob transaction, such as a batch poster | Charging its whole data bill to one unrelated user transfer |
| L2 user receipt | The rollup’s execution and applicable additional components | The user or the applicable sponsored flow | Assuming execution gas alone is always the total |
| Rollup batch record | Publication covering a set of L2 activity | The batch publication process | Assuming every user has an equal share of one blob |
| Wallet estimate | The wallet’s estimate for the proposed operation | No completed charge yet | Calling a maximum allowance the amount already spent |
One blob transaction can have two resource charges
EIP-4844 defines blob gas accounting in addition to execution gas. Blob cost is based on blob gas used and the applicable blob gas price; the execution portion remains a separate calculation. Both costs ultimately need a consistent currency unit before you add them. A count of execution gas units cannot be added directly to a count of blob gas units as if they were one resource.
For the execution component, the Ethereum gas explanation distinguishes the resource consumed from its price. The final cost uses the actual applicable price and use, not merely the maximum a sender was willing to authorize. Keep estimated limits, price caps and completed charges in separate columns when reconciling a receipt.
A fictional accounting example makes the distinction clear. Suppose the execution cost is 18 units of a common cost measure and the blob-data cost is 72 of those same cost units. The combined resource bill is 90. These are invented costs, not gas-unit counts, current prices or a valid transaction specification. Dividing that 90 equally by the number of people you think used a batch does not establish what the rollup charged your transaction.
Separate pricing does not mean a timeless rule of independence
Blob data and execution have distinct accounting, so one displayed price does not substitute for the other. But avoid turning that distinction into a claim that protocol pricing rules can never connect them. EIP-7918 describes a reserve-price mechanism linked to execution cost. Read the applicable network rules rather than assuming that an early explanation of the blob market settles every later pricing detail.
For a user checking a fee, the practical consequence is modest: identify the relevant resource and actual transaction first. You do not need to predict the next base fee to determine that an execution price and a blob price are different fields. Nor does a screenshot of a very low blob quote establish that an unrelated contract interaction should cost the same amount.
An L2 data charge is not a personal blob receipt
Arbitrum Nitro’s fee documentation distinguishes L2 execution costs from L1 data costs for sequencer transactions. The latter accounts for data publication and uses an attribution model involving the transaction’s estimated compressed size. A user-facing data charge is therefore not simply the entire fee from a batch poster’s L1 transaction copied into your wallet.
The publication method matters as well: the same documentation discusses posting through blobs or calldata. Do not assume that every transaction on every chain marketed as an L2 has identical data availability and fee treatment. Use the named chain’s current documentation. A label such as ‘L1 fee’ identifies a category to investigate, not a universal formula shared by all networks.
OP Mainnet’s current fee guide describes execution, L1 data and an operator component after the relevant upgrade. Its data-cost calculation reflects chain configuration and the applicable fee model. This is a concrete example of why multiplying one execution-gas figure by one price may omit part of the total. It is not a claim that every rollup has that same operator charge.
Read the completed charge without adding it twice
Open the receipt on the explorer for the correct chain and identify which fields are components and which field is a total. Etherscan’s blob explanation distinguishes blob transactions and their data context. An ordinary transfer and a batch publication can both be genuine records while answering different questions about the route.
If a rollup explorer already presents the total fee including a data component, adding that component again overstates the cost. If it presents only execution as the main field, omitting the documented additional components understates it. Resolve the display’s definition rather than assuming every explorer uses the same layout. A wallet maximum shown before submission is a third number and should not be labelled a completed charge.
- Identify the exact chain, transaction ID and sender role: user, L1 transfer or batch poster.
- Establish whether the transaction actually carries blobs or is a user operation accounted for on an L2.
- Separate execution use and price from blob use and price where those fields apply.
- For an L2, read that chain’s additional data or operator components and whether the explorer total includes them.
- Compare completed costs in the same currency and time context; keep estimates and maximum allowances separate.
- If a figure remains unexplained, ask about the named field and transaction instead of assuming the whole batch fee belongs to your transfer.
What this changes when preparing an exchange
A cheaper data-publication market does not make two deposit networks interchangeable. The receiving service must accept the specific asset and network, and the sending wallet must support the intended transfer. Comparing live receive amounts can be useful, but only among routes you can actually complete. A network’s name and a matching ETH symbol are not enough evidence of deposit compatibility.
For KOT.CASH, compare the fee explanation, exchange workflow and the actual receive estimate in simple swap. Do not add an invented ‘blob surcharge’ to an order or promise that cheaper blobs create a fixed service discount. These pages describe the service’s exchange process; the network receipt and any provider-specific breakdown address different parts of the cost.
FAQ
Does a low blob gas price make an ordinary Ethereum transfer cheap?
An ordinary L1 transfer pays execution costs rather than substituting a blob-data price for them. Check its own transaction estimate and receipt, not only a blob dashboard.
Are Ethereum blob fees the whole cost of an L2 transaction?
An L2 can charge execution and other applicable components as well as data publication costs. Read the named chain’s fee model and determine what the explorer includes in its total.
Is the Ethereum blob base fee a maximum I have already paid?
A current price, an authorized cap and a completed charge are different quantities. Use the applicable transaction fields and actual resource use to examine what was charged.