How to View Internal Transactions in Block Explorers
In block explorers such as Etherscan, find and click the 'Internal Txns' tab to see all value transfer records triggered by smart contracts under a wallet or transaction hash. This is execution-layer data not shown in regular wallets, and often the final answer to 'where did the money go?'.
Step 1: Understand the Difference Between 'Internal Transactions' and Regular Transactions
What to do: First understand what you are looking for.
How to do it:
Regular transactions are those you initiate and sign yourself, with an independent transaction hash (TxHash), visible directly under the 'Transactions' tab.
Internal transactions are subsequent value transfers triggered by a smart contract during the execution of a regular transaction. They do not have an independent transaction hash, are not user-signed, and do not appear separately in blocks; they are hidden in execution trace records.
Wallets usually only show the final result and do not expose internal transaction details. Block explorers read node-level execution trace data to reconstruct the calls and transfers occurring within contracts into a readable list.
Completion: You clearly understand that internal transactions are 'contract-triggered side effects,' not 'transfers you initiated proactively.'
Step 2: Find the 'Internal Txns' Entry on the Address Page or Transaction Details Page
What to do: Based on your query target, locate the internal transactions tab.
How to do it:
To view all internal transactions for an address: Enter the wallet address in Etherscan/BscScan → go to the address details page → find 'Internal Txns' in the tab bar (some interfaces may show 'Internal Transactions' or 'Internal Calls').
To see internal actions within a specific transaction: Enter the transaction hash (TxHash) to go to the transaction details page → similarly find the 'Internal Txns' tab, which will list all contract internal calls triggered by that transaction.
Completion: You have successfully opened the internal transactions list and can see several records.
Key Reminder: If a transaction goes through a cross-chain bridge, aggregator routing, or multi-layered contract calls, critical value changes often only appear in internal transactions or token transfer sections. Looking only at the outermost regular transaction record likely won't reveal where the funds went.
Step 3: Interpret Key Fields in the Internal Transactions List
What to do: Identify the core information of each internal transaction record, determining who triggered this fund flow and where it went.
How to do it: Each internal transaction record typically contains the following key fields:
| Field | Meaning | How to Read |
|---|---|---|
| Parent TxHash | The hash of the main transaction that triggered this internal transaction | Multiple internal transactions may belong to the same parent transaction |
| From | The sender of this internal value | Usually a contract address or the contract caller |
| To | The receiver of this internal value | Could be another contract or a regular wallet address |
| Value | Amount of native coin transferred (ETH/BNB, etc.) | Unit is usually the native token of the chain |
| Type | Call type (call / create) | 'call' means contract call, 'create' indicates a new contract was deployed |
| isError | Whether execution failed | '0' means success, '1' means failure |
Completion: You can locate a specific entry in the list and clearly state its source, destination, and amount.
Step 4: Distinguish Between 'Internal Transactions', 'Token Transfers', and 'Logs'
What to do: Understand the differences between the different tabs on a transaction details page so you don't look in the wrong place.
How to do it:
Internal Transactions: Contract-triggered value transfers where you can directly see the sending/receiving addresses and amounts, sourced from execution trace data.
Token Transfers: Transfer events for token standards like ERC-20/ERC-721, parsed from event logs emitted by contracts. If you're tracking non-native tokens like USDT, look at this tab, not internal transactions.
Logs: Raw event logs intentionally written by contract developers; most users do not need to view these.
Completion: You have confirmed whether you are looking for 'internal native coin transfers' or 'token transfers' and are viewing the correct tab.
Prerequisites
Before proceeding, make sure you have opened the correct block explorer and that the network you're searching on matches the chain where the transaction occurred. Searching an Ethereum transaction hash on BscScan will yield no results.
Common Failure Reasons
Only looking at the 'Transactions' tab and finding the amounts don't match: For example, the wallet sent 1 ETH, but the Transactions tab only shows a 0.01 fee deduction, while the internal transactions may show 0.99 ETH split and transferred to multiple addresses by the contract.
Mistakenly treating an internal transaction as 'another independent transfer': Internal transactions have no independent transaction hash; they are linked to the main transaction via Parent TxHash. If you copy an internal transaction's 'hash' and search for it, you'll find nothing.
Looking for token transfers in the wrong place: Records of non-native tokens like USDT transfers are under 'Token Transfers', not 'Internal Txns'.
Risk Reminder
Account Risk: Block explorers are read-only and involve no operational risk. However, when viewing internal transactions, do not click any suspicious links or copy contract addresses for authorization.
Fund Risk: No direct fund risk, but understanding internal transactions helps detect abnormal fund flows, such as when a DApp is attacked and funds may be moved out via internal transactions.
Compliance Risk: None.
Confirmation that you've done it correctly: You successfully found the 'Internal Txns' tab in the details page of the target address or transaction and can see the specific record list. If the transaction involves contract interaction but the list is empty, it means no native coin internal transfers occurred — the funds might have moved through token transfers, so check the 'Token Transfers' tab. Next step: If an unfamiliar receiving address appears in the internal transactions, that's a key clue for tracing where the money went — continue tracing that address.
