What does it mean when a token transfer shows zero value?

25 October 2026

A token transfer that displays zero value on a block explorer usually means the transaction transferred a token type the explorer does not recognise, or it moved tokens through a mechanism that hides the amount from the standard display. The value is not actually zero in most cases - the explorer simply cannot decode it.

Why explorers show zero for real transfers

Block explorers read on-chain data. For standard ERC-20 transfers, they parse the Transfer event, which includes the from, to, and value parameters. When a token contract follows the ERC-20 standard correctly, the explorer displays the amount.

Zero-value displays happen when:

• The token is non-standard. Some tokens implement Transfer events differently, omit the value parameter, or encode amounts in an unexpected format. The explorer sees the event but cannot extract the number.
• The token uses a proxy or upgradeable pattern. The transfer event may be emitted by the implementation contract while the explorer looks for it in the proxy contract. If the explorer does not trace the call properly, it may show zero.
• The token is an NFT (ERC-721 or ERC-1155). These use different event signatures. An ERC-721 Transfer event includes a tokenId instead of a value. If the explorer misidentifies the token standard, it may display the tokenId field as zero or leave the amount blank.
• The transaction involved a smart contract interaction, not a direct wallet-to-wallet send. When a contract moves tokens on your behalf - like a swap, deposit, or approval - the explorer may only show the internal call and fail to decode the transfer amount.
• The token is a rebasing or fee-on-transfer token. These tokens adjust balances internally. The Transfer event may log the gross amount before fees, but the explorer might show the net received amount as zero if it misreads the event data.

How to Verify the Real Amount

If you see a zero-value transfer and need to confirm what actually moved, follow these steps.

1. Check the Token Contract

Open the token contract address on the same explorer. Look for the Contract tab and read the source code if it is verified. Search for the Transfer event definition. If the event includes a uint256 value parameter, the token is standard and the explorer should display it. If the event is custom or missing the value field, that explains the zero.

2. Look at the Transaction Logs

Scroll to the Logs section of the transaction page. Every event emitted during the transaction appears here, raw. Find the Transfer event (or events) and examine the data field:

• For ERC-20: the data field contains the 256-bit hex value of the transfer amount. Copy it, convert from hex to decimal, and adjust for the token’s decimals. Many explorers let you click the hex value to see the decimal equivalent.
• For ERC-721: the data field is usually empty. The tokenId is in the indexed topics[3] field. The value is not a balance - it is a specific NFT identifier.
• For ERC-1155: the event includes both id and value in the data field. The value is the quantity transferred.

3. Use a Token-Aware Explorer or API

Some explorers specialise in token transactions. If your current explorer shows zero, paste the transaction hash into Etherscan (for Ethereum) or the equivalent for the chain you are using. Etherscan often decodes token transfers that other explorers miss. Alternatively, use a block explorer’s API to fetch the raw transaction receipt and parse the logs yourself.

4. Check for Internal Transactions

If the transfer was part of a contract interaction - like a swap on a decentralised exchange - the explorer may list the token movement under Internal Txns or ERC-20 Transfers separately. Look for a tab labelled Internal Transactions or Token Transfers. The amount may appear there even if it shows zero on the main transaction view.

When zero value is actually zero

There are legitimate cases where a token transfer truly moves zero tokens:

• Approvals. An ERC-20 Approval event is not a transfer, but some explorers mislabel it. The value is the approved allowance, which could be zero if the user is revoking approval.
• Mint or burn events. Some tokens emit Transfer events with from set to the zero address (for minting) or to set to the zero address (for burning). If the mint or burn amount is zero, the event is meaningless but still recorded.
• Failed internal transfers. If a contract attempts a transfer that reverts internally, the explorer may still show a zero-value event from a partial execution before the revert. Check the transaction status - if it shows Reverted, the transfer did not happen.

What to do next

If you are the sender or recipient and the explorer shows zero, do not assume the transaction failed or that nothing moved. Use the log inspection method above to extract the real value. If the logs confirm a non-zero amount, the transfer succeeded and the explorer is simply not displaying it correctly.

If the logs also show zero, check whether the transaction reverted. A successful transaction with a zero-value Transfer event is unusual but harmless - it may be a dust transfer or a test from the sender.

For any transaction where the displayed value does not match your expectation, always verify using the raw logs before taking further action.

Back to block explorers