Which Part of the Transaction Budget Is Actually Missing?

A wallet can display crypto and still lack the balance required by the transaction being attempted. The visible token may be on another network, locked, already committed to a pending transaction or unable to pay the fee. Start with the exact action and calculate its spendable transaction budget instead of treating the portfolio total as one balance.

Use the Spendable Transaction Budget

A transaction can proceed only when every required balance is available.

• Asset amount to send or spend
• Native gas or supported alternative fee asset
• Funds not reserved by pending activity
• Token allowance and contract preconditions
• Network-specific account or storage reserve
• Destination minimum and application requirements

Capture the exact error and action

Record whether the wallet is sending a native coin, transferring a token, swapping, approving, bridging or calling a contract. Insufficient funds for gas, insufficient token balance and insufficient output are different failures.

Cause 1 — the displayed asset is not the fee asset

An ERC-20 token balance normally cannot pay Ethereum gas. BNB Smart Chain uses BNB, Polygon uses POL and Avalanche uses AVAX. MetaMask currently offers gas-included transactions with other tokens on selected networks, but the option must appear in that wallet and transaction.

Cause 2 — the balance is on another network

ETH on Arbitrum, Base and Ethereum Mainnet are separate ledger balances even when the address is identical. The wallet can display an aggregate portfolio while the selected chain has too little native gas or none of the token.

Cause 3 — Send Max leaves no fee reserve

For native-coin transfers, the transaction amount and fee come from the same balance. Sending the entire displayed amount can leave nothing for gas. Use the wallet’s calculated maximum after fees rather than typing the full balance manually.

Cause 4 — a pending transaction reserves or blocks capacity

A submitted transaction can commit funds and occupy a lower nonce. Later EVM transactions may remain queued or fail in the wallet until the earlier nonce confirms, is replaced or is cancelled. Check the explorer before creating another request.

Cause 5 — the wallet balance is stale

RPC errors, an outdated selected account or a local pending record can make the interface disagree with the blockchain. Compare the exact address and network on a reputable explorer, then refresh or use the wallet’s documented reset procedure without changing keys.

Cause 6 — funds are locked or delegated

Staked, vesting, collateralized or time-locked assets can appear in portfolio totals without being spendable. On account-based networks, delegated or reserved balances can also reduce the immediately available native amount.

Cause 7 — the contract needs more than the token amount

A swap can require gas, allowance and enough input after slippage or transfer-tax behavior. A bridge can require source-chain gas and a minimum amount. The wallet’s generic error can mask an application rule discovered during simulation.

Cause 8 — token decimals or fee-on-transfer behavior differ

A custom token can use unusual decimals or deduct part of the amount during transfer. Use the verified contract and fresh application quote. Do not edit token metadata merely to make the balance look larger.

Cause 9 — the receiver or protocol enforces a minimum

Some wallets label a transaction impossible when the amount fails a protocol reserve, rent, storage or dust rule. Exchanges and bridges can also reject values below their current minimum even when the blockchain balance is adequate.

Use the Network–Asset–Available table

Write one row for every required quantity.

• Selected network and chain ID
• Asset contract or native coin
• Displayed total
• Explorer-confirmed balance
• Pending or locked amount
• Available amount
• Estimated fee
• Required application minimum

Fix only the missing row

Add native gas only when the correct network balance is genuinely short. Reduce the send amount when the fee shares the same native balance. Clear a pending nonce when it blocks later transactions. Unlock or wait when the funds are not spendable.

Do not bridge or swap blindly to fix gas

A bridge and swap themselves require fees and can introduce approvals, slippage and another network. Use a wallet-supported gas-included mode or a small verified native-asset transfer only when it is cheaper and safer than the alternatives.

Worked token-gas mismatch

A wallet shows 30 USDC on Ethereum and zero ETH. A standard token transfer is greyed out. The missing quantity is Ethereum gas, not USDC. The user uses an official supported gas-included option or obtains a small amount of ETH after checking the fee.

Worked wrong-network balance

The user sees 0.01 ETH in the portfolio but the transaction is on Base, where the address holds zero ETH. Switching to Ethereum Mainnet reveals the source of the displayed amount. The Base transaction remains unfunded.

Worked pending-nonce block

An earlier Ethereum transaction with a low fee remains pending. The wallet’s later transaction cannot proceed normally. The user verifies the nonce and uses the wallet’s Speed Up or Cancel path rather than adding unrelated tokens.

Worked false portfolio confidence

A wallet shows $100 across staked tokens and a locked reward position but only $0.02 of available native gas. The portfolio value is real, yet the immediate transaction budget is insufficient.

The error decision

The balance is sufficient only when the correct asset, correct network, spendable amount, fee capacity and application conditions all pass at the same time. Fix the failed row or abandon the transaction when the required funding exceeds its value.

Insufficient-funds references checked on July 30, 2026

Current MetaMask documentation supports the native-gas, gas-included and pending-transaction branches used in the budget.

• MetaMask insufficient-funds and gas-included transaction guidance: https://support.metamask.io/configure/transactions/how-to-fix-insufficient-funds-error-or-greyed-out-confirm-button/
• MetaMask transaction and network error codes: https://support.metamask.io/configure/networks/error-internal-json-rpc-error-when-trying-to-interact-with-other-networks/
• MetaMask speed-up and cancellation process: https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction/
• MetaMask account reset for local pending history: https://support.metamask.io/configure/accounts/resetting-your-account-in-the-event-of-a-stuck-or-pending-transaction/
• TRON resource model for token transactions: https://developers.tron.network/docs/resource-model

FAQ