Ethereum Glossary: How ETH, Gas, Transactions and Smart Contracts Work

Ethereum terminology becomes easier once the words are treated as parts of one process rather than isolated definitions. Start with the asset being moved, identify the network that records it, examine the signed action, and then use the transaction hash to verify the result. This map helps distinguish what you own, what you pay, what code executes, and what evidence appears onchain.

Core Ethereum Glossary

Ethereum: Exact meaning: A programmable blockchain network that maintains a shared state and executes transactions and smart-contract code. In plain English: Ethereum is the environment in which accounts, ETH, tokens and applications interact. Where it appears: Wallet network selectors, technical documentation, exchange deposit instructions and block explorers. Decision affected: Which network must be selected before sending an asset or interacting with a contract. Independent networks can follow Ethereum-compatible rules without sharing balances or transaction history with Ethereum Mainnet. ^[1]
Blockchain: Exact meaning: An ordered record in which transactions are grouped into blocks linked to previous blocks through cryptographic references. In plain English: It is the shared history from which Ethereum nodes calculate the current state of accounts and contracts. Where it appears: Explorer block pages, transaction histories and descriptions of network confirmation. Decision affected: Whether to rely on a wallet notification alone or verify that a transaction has actually been included in the chain. ^[2]
ETH or ether: Exact meaning: The native coin of Ethereum. ETH can be transferred between accounts and is used to pay transaction fees on Ethereum Mainnet. In plain English: ETH is both an asset and the standard payment resource for computation performed by the network. Where it appears: Account balances, transfer amounts, fee estimates and explorer records. Decision affected: Whether an account has enough ETH to cover both the intended action and its network fee. Ethereum records ETH amounts internally in smaller denominations, including wei. ^[3]
Coin: Exact meaning: A blockchain’s native asset; on Ethereum, that asset is ETH. In plain English: A coin belongs to the network itself rather than being represented by a separately deployed token contract. Where it appears: Asset descriptions, wallet balances and comparisons between ETH and ERC-20 assets. Decision affected: Which asset is needed for gas and whether a contract address must be checked before receiving or swapping an asset. ^[4]
Token: Exact meaning: An asset whose balances and transfer rules are managed by a smart contract rather than by Ethereum’s native ETH accounting. ERC-20 is a common standard for fungible tokens. In plain English: A token exists through contract logic running on Ethereum. Where it appears: Token contract pages, approval requests, wallet asset lists and decentralized applications. Decision affected: Whether the correct contract address has been selected and whether a separate approval transaction is required before a contract can spend the token. ^[5]
Account: Exact meaning: An Ethereum entity with a balance and state. Ethereum distinguishes externally owned accounts controlled by signing keys from contract accounts controlled by code. In plain English: One type represents a user-controlled source of transactions; the other represents a deployed program. Where it appears: Wallets, explorers, contract documentation and transaction records. Decision affected: Whether an address is simply receiving assets or will execute contract logic when called. ^[3]
Address: Exact meaning: A public identifier for an Ethereum account. Both user-controlled accounts and smart-contract accounts have addresses. In plain English: It is the destination shown when sending ETH, tokens or a contract instruction. Where it appears: Wallet receive screens, deposit instructions, transaction details and contract pages. Decision affected: Where the transaction will go and whether the destination belongs to the intended account or contract. An address is public, but it does not prove by itself that the selected network is correct. ^[3]
Wallet: Exact meaning: Software or hardware used to interact with an Ethereum account and manage transaction signing. A wallet is not the account itself. In plain English: It is the interface through which a user reads balances, reviews requests and authorizes actions. Where it appears: Browser extensions, mobile applications and hardware devices. Decision affected: What information is reviewed before signing and how private keys are protected. ^[3]
Private key: Exact meaning: Secret cryptographic data used to authorize transactions or messages for a particular account. In plain English: Whoever controls the private key can approve actions from the associated account. Where it appears: Usually inside wallet key management rather than in ordinary transaction screens. Decision affected: Whether an action can be signed securely. A private key must never be entered into an exchange form, block explorer, unsolicited website or support chat. ^[3]
Seed phrase or recovery phrase: Exact meaning: Recovery information from which a wallet can derive and restore account keys. In plain English: It may provide access to multiple accounts in the wallet, not merely one address. Where it appears: Wallet creation, backup and recovery procedures. Decision affected: How the wallet can be restored and how broadly a disclosure could compromise funds. No legitimate recipient needs a seed phrase to receive ETH. ^[6]
Transaction: Exact meaning: A cryptographically signed instruction that requests a change to Ethereum’s state. A transaction can transfer ETH, deploy a contract or call a function on an existing contract. In plain English: It is an authorized request asking the network to perform an action. Where it appears: Wallet confirmation screens, pending activity lists and explorer transaction pages. Decision affected: Whether the recipient, value, contract call, network and maximum fee are acceptable before signing. ^[4]
Smart contract: Exact meaning: Code and state deployed at a specific address on Ethereum. A contract executes its programmed functions when it receives an appropriate call. In plain English: It is an onchain program that can transfer tokens, record data or enforce application rules. Where it appears: Token contracts, decentralized exchanges, lending applications, NFT systems and approval requests. Decision affected: Which code receives authority and what state-changing action will occur after the transaction is accepted. Contract interactions are generally irreversible, and code may contain defects or unwanted permissions. ^[7]
Ethereum Virtual Machine or EVM: Exact meaning: The execution environment used by Ethereum nodes to process smart-contract code consistently. In plain English: The EVM is the engine that interprets contract instructions. Where it appears: Developer documentation, gas explanations and descriptions of EVM-compatible networks. Decision affected: Whether an action is a simple asset transfer or a potentially more complex contract execution. ^[8]
Gas: Exact meaning: A unit measuring the computational work required to process an Ethereum operation. In plain English: More complex actions generally consume more gas units than simpler ones. Gas measures work; it is not itself an additional token. Where it appears: Wallet estimates, transaction details, smart-contract documentation and explorer receipts. Decision affected: How much computation a transaction may use and whether the account can cover the resulting fee. ^[4]
Gas limit: Exact meaning: The maximum quantity of gas units a transaction is permitted to consume. In plain English: It is a safety ceiling for computation, not necessarily the quantity that will be used. Where it appears: Advanced wallet settings and explorer transaction data. Decision affected: Whether the transaction has enough execution capacity. Unused gas is not treated as consumed, while an inadequate limit can prevent the requested execution from completing. ^[4]
Transaction fee: Exact meaning: The amount paid for the gas actually consumed, priced in ETH under the transaction’s fee parameters and current network conditions. Modern Ethereum transactions can specify a maximum total price per gas unit and a maximum priority component. In plain English: Gas counts the work; the fee is what that work costs. Where it appears: Wallet previews and explorer fields such as gas used, base fee and effective gas price. Decision affected: Whether to submit now, wait, or reject an unexpectedly expensive request. The maximum shown before signing may be higher than the final charge. ^[4]
Transaction hash, tx hash or txid: Exact meaning: A cryptographic identifier generated for a submitted transaction. In plain English: It is the lookup reference used to follow a transaction independently of a wallet’s status message. Where it appears: Wallet histories, exchange records and blockchain explorers. Decision affected: Whether the transaction can be verified, whether it is pending or included, and which exact onchain action is being discussed. ^[4]
Confirmation and finality: Exact meaning: Inclusion places a transaction in a block; later blocks and Ethereum’s consensus process increase confidence that the recorded result will not be replaced. Protocol finality is stronger than a service’s informal count of “confirmations.” In plain English: A broadcast transaction is not the same as an included transaction, and an included transaction continues to gain settlement assurance. Where it appears: Explorer status pages and deposit-processing policies. Decision affected: When a recipient or service treats an incoming transfer as sufficiently settled. Different services may apply different acceptance thresholds. ^[2]

Relationship Map: From ETH to a Verifiable Result

The following chain connects the glossary terms in the order a real Ethereum action normally follows:

Object: Choose what is being moved or changed. It may be native ETH, a token balance managed by a contract, or another piece of contract state.
Network or environment: Select the network specified by the recipient or application. The same account address can be recognized on multiple EVM-based networks, but balances and transaction histories do not automatically move between them. ^[1]
Action: The wallet builds a transaction containing details such as the destination, transferred value, contract input data and fee parameters. The account authorizes that transaction with a signature. ^[4]
Execution: A direct ETH transfer updates account balances. A contract call asks the EVM to run code, which may update token balances, emit events or perform several internal operations. State-changing execution consumes gas. ^[7]
Confirmation: The signed transaction is broadcast, waits for inclusion and is processed in a block. A transaction hash allows the sender and recipient to follow this lifecycle. ^[4]
Verifiable result: A block explorer can show the network, sender, destination, status, block, transferred value, gas used and contract-generated events where applicable. The useful evidence is the onchain result, not merely a “sent” message in one interface.

How common Ethereum actions fit the map
Object	Network action	Role of gas	Result to verify
ETH	Transfer from one account to another	Pays for processing the transaction	Correct recipient, value, status and block inclusion
ERC-20 token	Call the token contract’s transfer function	Pays for contract execution	Correct token contract, recipient and token-transfer event
Token approval	Authorize a contract to spend up to a stated allowance	Pays for changing the allowance stored by the token contract	Correct spender contract and acceptable allowance
Decentralized swap	Call one or more contracts to exchange assets	Pays for the full execution path	Transaction status, assets received, amount, events and remaining approvals
Contract read	Query existing state without changing it	A local or remote read generally does not create an onchain fee for the user	Returned data rather than a new transaction hash

Ethereum documentation distinguishes contract reads from state-changing writes. A read can query existing information without creating a transaction, while a write requires onchain execution and normally incurs a fee. A wallet may still request a signature for an offchain message, so the presence of a signing prompt alone does not prove that a gas-paying transaction is being created. ^[9]

Do Not Confuse These Terms

Closely related concepts with different practical consequences
Pair	The difference	Consequence of confusion
Ethereum vs ETH	Ethereum is the network and execution environment; ETH is its native coin.	A user may choose an asset correctly but send it through a network that the recipient does not support.
Coin vs token	ETH is native to Ethereum. An ERC-20 token is represented by a smart contract with its own contract address.	A ticker or asset name can be copied by unrelated contracts. Failing to verify the contract may result in acquiring or sending the wrong token.
Asset vs network	The asset is what is transferred; the network is the ledger and execution environment used for the transfer.	Selecting “ETH” does not by itself identify the required network. A service may accept ETH on one network but not another, and recovery from an unsupported-network deposit may be unavailable.
Address vs network	An address identifies an account within a network context. Similar address formats can appear across independent EVM networks.	A syntactically valid address can still be used on the wrong network. Always confirm both pieces of information.
Wallet vs account	An account exists in Ethereum’s state; a wallet is a tool used to access and control accounts.	Deleting a wallet application does not delete the onchain account, but losing all valid recovery access can make the account unusable.
Seed phrase vs private key	A private key controls a particular account. A seed phrase commonly restores a wallet structure from which multiple account keys may be derived.	Exposing a seed phrase may compromise more accounts than exposing one individual private key. Neither should be shared. ^[10]
Gas vs transaction fee	Gas is the quantity of computational work; the fee is the amount of ETH charged for consumed gas.	A number of gas units should not be read as an amount of ETH. Fee assessment requires both gas consumption and the price paid per unit.
Gas limit vs gas used	The limit is the permitted ceiling; gas used is the computation actually consumed.	The maximum estimate may be mistaken for the final charge, or an unsafe manual limit may prevent successful execution.
Fee vs slippage	The network fee pays for execution. Slippage is the difference between an expected swap result and the result permitted or obtained as market conditions and liquidity change.	A transaction can have an acceptable fee but an unacceptable exchange outcome. Paying more gas does not guarantee a better token price or deeper liquidity.
Transaction vs exchange request	An Ethereum transaction is a signed onchain instruction. An exchange request or order is a service-level instruction that may involve separate deposit, conversion and withdrawal stages.	A completed blockchain deposit does not necessarily mean every subsequent service operation is complete. Each stage needs its own status check.
Broadcast vs confirmation	Broadcast means the network has received the transaction request; confirmation requires inclusion in a block.	A txid alone does not prove successful execution. The transaction can remain pending, be replaced, or be included with a failed execution status.
Inclusion vs successful execution	Inclusion records the transaction in a block. The execution status shows whether the requested state change completed.	A failed contract call can be recorded onchain without producing the intended token transfer, while still consuming computational resources.
Address vs Memo or Tag	A basic Ethereum transaction has a destination address and optional input data, but no universal destination-tag field equivalent to those required by some other asset networks.	Do not invent a Memo or Tag for an ETH deposit. If a receiving service supplies additional instructions, follow that service’s exact requirements rather than assuming rules from another blockchain.

How Gas and Smart Contracts Fit Together

Gas prevents arbitrary computation from being free. Every operation performed by the EVM has a computational cost expressed in gas units. A simple transfer and a multi-step contract call therefore need not consume the same amount. The final fee depends on the gas actually used and the applicable price per gas unit, paid in ETH. ^[4]

A smart contract does not independently decide to charge a network fee. The fee arises because Ethereum nodes must execute the transaction. Contract code can also transfer assets or impose application-level charges according to its own rules, but those amounts are separate from gas. A wallet preview should therefore be read as a set of distinct effects: assets sent, contract permissions granted, application terms and the Ethereum network fee.

Why a failed contract call can still cost ETH

Execution uses network resources even if contract logic rejects the requested state change or runs out of permitted gas. The intended action can fail while the transaction itself remains visible in a block. This is why checking only for a txid is insufficient: the explorer’s execution status and resulting token events matter as well.

Why token transfers need ETH

An ERC-20 transfer changes records maintained by a token contract. The token being sent does not automatically replace ETH as the network’s fee asset. Under the ordinary Ethereum transaction model, the sending account needs sufficient ETH for gas even when the transferred asset is DAI, USDT or another token. Some account-abstraction arrangements can sponsor or restructure fee payment, but that is an application-specific mechanism rather than a reason to assume every wallet or service supports gasless transfers. ^[5]

Practical Example: Preparing an ETH Exchange

Suppose you want to exchange ETH for another supported asset. Before creating a request, check the currently available ETH exchange direction, including the required deposit and receiving networks. The service lists ETH alongside assets such as USDT, BTC, DAI, LTC, BNB, XMR and TRX, but this does not mean every possible pair, network or direction is available at all times.

Identify whether you hold native ETH or a token with a similar name or ticker.
Read the exchange instructions for the exact deposit network rather than selecting a network based only on address format.
Copy the deposit address from the active request and compare it carefully before signing.
Review the ETH amount and the separately displayed network fee.
Send only through the specified network. A transfer through an unsupported network may not be credited and may not be recoverable.
Save the txid and inspect it in an explorer for the same network.
Confirm that the destination, value and execution status match the request.
Allow for the receiving service’s required confirmation or compliance process. Requirements can depend on the operation direction and the results of applicable checks, so they should be reviewed before the request is created.

This example does not require a smart contract if the action is a direct ETH deposit to an address controlled by the receiving service. By contrast, an onchain decentralized swap normally calls one or more contracts and introduces additional checks: contract identity, token approval, minimum received amount, liquidity, slippage tolerance and contract risk.

Recognition Checklist for Wallets, Documentation and Explorers

Before signing in a wallet

Network: Match it to the recipient’s written instructions. Do not rely only on the familiar 0x address format.
Action type: Determine whether the request is an ETH transfer, token transfer, token approval, contract call or message signature.
Destination: Check whether the address belongs to the intended recipient or to a contract.
Asset and amount: Separate the value being transferred from the ETH reserved for gas.
Contract permissions: For an approval, inspect which contract will become the spender and how much it may spend. Avoid granting an unlimited allowance without understanding why it is requested. ^[10]
Fee estimate: Treat it as an estimate or maximum under the wallet’s stated parameters, not as a permanent Ethereum fee.
Unexpected requests: Reject any page or person asking for a seed phrase or private key. Those secrets are not required to receive assets, check a transaction or complete ordinary account verification. ^[10]

When reading technical documentation

“Read,” “call” or “view”: Usually indicates querying contract state without creating an onchain state change.
“Write,” “send transaction” or “execute”: Indicates a state-changing action that must be authorized and processed.
Contract address: Identifies the deployed code instance. The same application can use different addresses on different networks.
Token standard: Describes a contract interface, not the legitimacy or market value of a particular token.
Gas estimate: Predicts execution requirements but cannot remove contract, network or market risk.
Approval or allowance: Grants spending authority; it is not the same action as transferring the approved tokens.

After submission in a block explorer

Open the transaction by its txid on an explorer for the selected network.
Compare the sender and destination with the intended accounts.
Check whether the status is pending, successful or failed.
Confirm the transferred ETH value separately from the transaction fee.
For tokens, verify the token contract and transfer event rather than relying solely on the displayed symbol.
For contract calls, review the called contract, decoded function if available, emitted events and any token movements.
Check block inclusion and distinguish it from the recipient service’s own required confirmation threshold.
If the transaction is absent, first verify that the explorer is connected to the same network used by the wallet.

Working Rule

For any Ethereum operation, verify five items in order: asset → network → destination or contract → signed action and fee → txid and execution result. ETH is the native coin, gas measures computation, the fee pays for that computation, and smart contracts define the programmable action. None of those checks substitutes for another. A correct address on the wrong network, a valid txid with failed execution, or a successful contract call granting excessive authority can each produce a different unwanted outcome.

Ethereum transactions are generally irreversible, while phishing pages and malicious contracts can imitate legitimate interfaces. Confirm instructions through trusted channels, keep recovery secrets offline, and treat network compatibility and contract permissions as transaction-critical data rather than optional technical details. Rules for exchange access, compliance and crypto taxation also vary by country and service, so operational requirements should be checked for the user’s jurisdiction before funds are sent. ^[10]