An Ethereum send can mean transferring ETH or moving a token recorded by a smart contract. The wallet interface may make these actions look similar, but the asset movement and fee budget need separate checks. A token balance does not automatically provide the native currency needed to execute an ordinary transaction.
This guide explains how to review an ETH or ERC-20 transfer on Ethereum mainnet. It also shows why a familiar address or token ticker is insufficient when several networks are available. For the broader preparation sequence, start with the Ethereum send guide and keep the recipient's current receiving instructions beside the wallet review.
Identify the asset and network together
Before entering an amount, write down what the recipient expects: the asset, the blockchain, and the destination address. For a token, confirm the contract identity on that blockchain. Token symbols are labels, and similar labels can appear in different contracts or on different networks. Treat the token's identity as part of the transfer instruction.
Ethereum mainnet and networks compatible with Ethereum tooling are separate destinations. An address that fits an Ethereum wallet's format does not prove that a receiving exchange supports the chosen network or token. If an exchange offers several withdrawal networks, select only a route that the receiving account explicitly accepts. Its deposit instructions take priority over assumptions based on branding.
Do not assume changing the selected network moves an existing balance. First establish where the asset currently exists and where it needs to arrive. If these differ, review the cross-chain altcoin send guide before proceeding. The route may involve additional transactions and costs that a simple same-network transfer does not cover.
ETH and ERC-20 transfers use different transaction details
ETH is Ethereum's native asset. A straightforward ETH payment specifies the recipient and the amount of ETH to move. A standard ERC-20 token transfer instead calls the token contract's transfer function, providing the recipient and token amount. The contract updates its token records when that operation succeeds.
This difference matters when reading an explorer. A token transfer can have the token contract as the transaction's top-level destination and no native ETH payment value. The intended token recipient appears in the token transfer details. Check the token movement, contract identity, and recipient together rather than reading one field in isolation.
The token contract address identifies the asset's software. It is not automatically the address where a person or exchange wants a deposit. Use the receiving address supplied for the actual destination. If a transaction preview differs from what you expected, stop to understand the action before signing. Labels should help explain the transaction, not replace reviewing it.
Why an Ethereum send needs a gas budget
Gas measures the computational work of an Ethereum transaction. Network fees are paid in ETH, including when the transaction transfers an ERC-20 token. In an ordinary self-custody send, the sending account therefore needs enough ETH for the fee as well as enough of the asset being transferred.
The fee follows the amount of gas used and the effective price per gas. Ethereum's fee mechanism includes a protocol base fee and a priority component. The official Ethereum gas and fees documentation explains these components and why the fee can change with network demand.
Read the fee currency explicitly. Having the right token balance on Ethereum does not establish that your ETH budget is adequate. Similarly, an ETH balance displayed for another network should not be counted toward the mainnet transaction. Base the review on the account and network actually shown in the signing request.
Separate the gas limit from the price per gas
The gas limit caps the computational units available to the transaction. A maximum fee per gas caps the price the sender authorizes per unit. These are different controls. Reducing a transaction's gas limit indiscriminately does not make the intended computation cheaper; it can prevent execution from completing.
A wallet may show an estimated fee alongside a maximum authorized fee. Establish which figure you are reading before comparing options. Avoid copying a gas limit from an unrelated ETH payment into a token transfer. A token contract call performs its own work, and a transfer involving a smart contract may need more computation than a basic payment between ordinary accounts.
Use the wallet's current transaction estimate as the starting point. If the estimate is unexpectedly high or simulation reports a problem, inspect the recipient, asset, and operation before changing advanced settings. An unexplained cost deserves investigation, especially when the transfer amount is small relative to the proposed fee.
Plan what remains after the send
When sending ETH, review the recipient amount and fee together so the total fits the account's available balance. When sending tokens, review the token debit and ETH fee as two separate balances. The final preview should make clear what leaves the account and what should remain afterward.
Consider the next action as well. If you intend to move several tokens, emptying the available ETH before those transfers can leave no fee budget for an ordinary later send. Plan the sequence using current estimates and recheck before each transaction. Avoid treating an earlier estimate as a permanent allowance for every later operation.
A receiving account may also need ETH for an ordinary future outgoing transfer. If the recipient is new to self-custody, establish whether they understand how they will move the asset later. Receiving the expected token and being prepared to send it onward are separate practical requirements.
A token approval is a separate permission
The ERC-20 interface distinguishes transferring tokens from approving another spender to use them. An approval sets a spending allowance. By itself, it does not deliver the intended payment to the recipient. This explains why a wallet can show a successful approval while the token balance has not moved.
A direct transfer from a conventional wallet normally does not require granting an unrelated application a broad token allowance. If a supposed send asks for an unfamiliar spender or an unexpectedly large permission, inspect the workflow. There may be an additional application operation involved, and it should be understandable before you authorize it.
Review what the request permits, which contract receives that permission, and how it relates to the task. A signature request should not be treated as routine merely because it appears after connecting a wallet. Keep transfer confirmation separate from approval confirmation in your own records.
Read the transaction outcome before sending again
A transaction hash identifies a submitted transaction; it does not prove that the intended operation succeeded. Open the record on the correct network and read its status, sender, destination, and asset movement. For a token transfer, also verify the token recipient and amount shown by the contract's transfer record.
If an included transaction fails during execution, it can still consume gas even though the intended asset movement does not complete. A wallet rejecting a request before broadcast is a different situation. Establish which event occurred before assuming the fee was charged or the token was sent.
Ordinary Ethereum account transactions use a nonce, a sequential transaction number. A pending earlier transaction can affect later transactions from the same account. Diagnose the sequence in the wallet's activity history before attempting repeated sends. The pending transfer guide explains how to gather the record needed for a useful diagnosis.
Check the receiving service separately
A successful token movement does not by itself prove that a hosted account has credited the deposit. Compare the network and token contract with the service's accepted deposit instructions, then check its confirmation requirement and deposit status. If support is needed, provide the transaction hash, asset, network, amount, and receiving address through the service's established channel.
For a new destination, the wallet address and network checks can help you review those details before the first send. Never provide a recovery phrase or private key to establish ownership of a routine deposit.
Conclusion: verify the movement and its execution cost
A clear Ethereum send review identifies the exact asset on the exact network, separates its amount from the ETH fee, and explains every requested permission. After submission, verify the transaction outcome and the recipient's actual credit. These checks make both native ETH payments and ERC-20 transfers easier to understand without assuming that every wallet screen describes the same operation.
