Technologie & IA
Gas and network fees: why does a transaction cost money?
Fees compensate or regulate the use of blockchain resources. Their calculation depends on the network, the operation and demand at the time.

Resources and execution costs
Sending cryptoassets or using an application consumes blockchain resources. Fees help limit abusive activity and contribute to the network's economic operation. Calculations vary across protocols. Gas describes a particular mechanism on Ethereum, although the word is sometimes used more loosely when discussing other networks. Understanding a fee begins with identifying the network and the action being requested.
02How it works+
On Ethereum, gas measures the work required to execute an operation. A simple transfer and a complex interaction with several contracts require different resources. Cost depends on gas consumed and the price per unit, rather than necessarily being proportional to the value transferred. Moving a larger monetary amount does not automatically mean that the same type of operation requires proportionally more computation.
Execution fees include a protocol base component and a priority component for the validator. The base component is burned. The unit price is often expressed in gwei, a subdivision of ether. When demand for space rises, costs can change quickly. A gas limit restricts the resources authorised for the operation; it is different from the unit price and the final amount paid.
03Key points to remember+
Different networks and fee components
An executed transaction that fails can consume resources and incur fees even when the intended contract changes are reversed. Other networks have their own models. Solana transactions pay fees in SOL, including a base component and an optional priority component. A secondary network can also include costs associated with publishing data on another blockchain. Fee names alone do not provide a complete comparison.
The token being transferred and the asset used to pay the network can differ. A wallet can therefore contain tokens without holding the asset needed to send them. Platform or application charges may also be added to network fees. These components need to be separated from exchange price effects. A meaningful comparison uses the same units and equivalent operations, with a clear account of what each interface includes.
Imagine two requests sent at the same time: a simple transfer and an interaction involving several contract functions. Their complexity can differ even if the transferred value is identical. The estimated quantity of resources and the proposed price for those resources are separate parameters. This distinction helps explain why superficially similar requests can produce different costs without either being a percentage charge on the transferred amount.
Estimates and final execution
The figure shown before signing is an estimate based on observed or expected conditions. It does not necessarily describe a completed execution. Final status, consumed resources and applied charges provide another kind of information. The initial estimate and the final record should be read as different stages of the same process, rather than assumed to be interchangeable descriptions of an operation that has already happened.
A failed execution after resources have been used also differs from a user declining to sign before submission. The screen can show an unsuccessful action in both situations, while the network activity differs. Reading the result alongside the transaction record explains what was actually attempted and charged. Network fees, service commissions and price effects each contribute their own information to that account.
