Why do transactions cost gas?

Gas measures the work required to execute an operation on a network.

A simple transfer uses little; a complex interaction across contracts uses more.

Gas is not an arbitrary tax: it rations computation and protects the network from spam.

Cost has two parts: gas units used and the price offered for each unit.

The wallet estimates the work and sets a limit; only units actually consumed are charged.

The final bill is paid in the network's native asset.

Each block has limited space while requests can all arrive at once.

When the network fills, users compete for priority by offering a higher price.

The same action therefore costs differently across networks, times and activity levels.

A higher tip can speed up inclusion without guaranteeing an exact moment.

A low price leaves the transaction pending until demand falls.

A failed operation may still consume gas because computation genuinely took place.

Amount sent — what the recipient receives

Network fee — what execution costs

Estimated speed — a probability, not a promise

Gas limit — the allowed computation ceiling

Compare compatible networks or layer-two systems.

Wait for a quieter period when the action is not urgent.

Batch operations when the protocol supports it.

Keep enough native asset so the rest of the wallet does not become stranded.

Gas is the live price of a scarce resource: secured computation space.

Compare the fee with the value of the action, not just the transferred amount.

Reading the quote before signing avoids most unpleasant surprises.