What Is an Internal Transaction, and When Does Your Explorer Hide It?

10 October 2026

An internal transaction is a transfer of value that happens inside a smart contract, not as a top-level transaction signed by a wallet. An explorer hides it when it only shows external transactions by default, or when the internal transfer is a side effect of a complex call like a token swap or a multi-step DeFi operation. To see it, you usually have to switch to a separate tab labeled "Internal Txns" or "Logs."

How internal transactions differ from external transactions

A standard explorers/transaction-lifecycle-block-explorer/">blockchain transaction - sometimes called an "external transaction" - is initiated directly by a wallet address. It has a nonce, a signature, and appears immediately on the transaction list of any block explorer. An internal transaction has none of these. It is not signed by a wallet, does not consume a separate nonce, and is not recorded as a standalone entry on the chain. Instead, it exists only as a trace inside another transaction.

The most common example is a token transfer via a smart contract. When you send an ERC-20 token from your wallet, you do not send the token directly. You call a function on the token contract, which then updates its internal ledger. That update is an event, not a transfer of native currency. But if the contract also sends ETH as part of that call - for example, to pay a fee to another contract - that ETH movement is an internal transaction.

Another frequent case is a decentralized exchange swap. You send ETH to a router contract. That contract then calls a liquidity pool contract, which sends tokens back to you. The initial ETH send is external. The ETH movement from the router to the pool, and the token movement from the pool to your wallet, are both internal transactions.

When and why explorers hide them

Block explorers are designed to show the clearest possible view of on-chain activity. For most users, the main transaction page lists only external transactions. Internal transactions are hidden for several practical reasons:

• Volume. A single complex transaction can contain dozens or even hundreds of internal transfers. Listing them all on the main page would overwhelm the normal view.
• Relevance. Most users only need to know that their transaction succeeded and what the final balance change was. The intermediate steps are noise.
• Cost. Storing and indexing internal transaction traces requires extra processing. Some explorers limit this to paid tiers or only show them for a certain time window.

The most common scenario where a user needs internal transactions is when they see a transaction that appears to have no effect. For example, you send ETH to a contract address, and the explorer shows the transaction as successful, but your wallet balance shows no change. The contract may have forwarded that ETH to another address as an internal transaction. Without checking the internal tab, you cannot trace where the money went.

How to Find Internal Transactions on Major Explorers

The method varies by explorer, but the pattern is consistent. Here is the general procedure:

1. Open the transaction on the explorer. Navigate to the transaction hash using the search bar.
2. Look for a tab or link labeled "Internal Txns" or "Internal Transactions." On Etherscan, this tab is usually next to "Logs" and "State." On BscScan, it is labeled similarly. On block explorers for other EVM chains, the tab may say "Trace" or "Internal Calls."
3. Click that tab. The page will reload to show a table of internal transactions. Each row will show a "From" address, a "To" address, the value transferred, and the gas used by that internal call.
4. If no tab appears, the explorer may not support internal transaction lookups for that transaction, or the transaction may not have triggered any. Some explorers also hide internal data behind a "Click to show" button to reduce load.

For non-EVM chains, internal transactions may not exist in the same sense. On Bitcoin or other UTXO-based chains, there is no concept of a smart contract call. Internal transactions are specific to account-model chains like Ethereum, Binance Smart Chain, Polygon, Avalanche, and others that support the Ethereum Virtual Machine (EVM).

When you should check internal transactions

You should check internal transactions whenever you suspect that value moved in ways the main page does not show. Typical situations include:

• You sent native currency to a contract and the contract sent it elsewhere. The main page will show the outgoing transaction from your wallet. The internal tab will show the contract's subsequent transfers.
• You interacted with a multi-step DeFi protocol. For example, depositing into a lending protocol may trigger internal transfers between the lending pool, a reward contract, and a fee collector.
• You see a transaction with a zero value but a high gas fee. The value field on the main page only shows the native currency sent. If the transaction's purpose was to interact with a token contract, the actual transfer of tokens is an internal event, not a value transfer.
• You need to verify that a bridge or swap completed correctly. The internal tab shows each hop the value took, including any wrapped tokens or intermediary addresses.

A useful habit: whenever you are troubleshooting a transaction that seems incomplete, open the internal tab before blaming the protocol or your wallet. The information is almost always there - just not on the main page.

Back to block explorers