How it works
Transaction Details
What a transaction did in one sentence, who took part, what it cost, every transfer, and the signals worth a look.
Updated 2026-10-10
Overview
Every transaction on a supported network has a page at /<network>/tx/<hash>. It reads the transaction from the network's explorer and lays out what happened. Nothing is signed and no wallet is needed.
- Summary: one sentence, such as 0x12…ab swapped 0.5 ETH for 1,350 USDC on Uniswap, built from the transfers by the same rules as the wallet tables' Activity column.
- Signals: a failure and its revert reason, an EIP-7702 delegation, an unlimited or collection-wide approval, look-alike addresses, zero-value and spam token transfers.
- Overview: status, time, block, sender and recipient (or the contract created), method and value.
- Sender's asset changes: what left and what reached the sender's wallet.
- Fee and gas: the network fee, gas used and price, nonce and transaction type.
- Permissions, decoded input and every token and coin transfer, each address with its name and a link to its wallet or contract page.
You reach it from search (Ctrl/Cmd+K with a transaction hash), from Open the transaction page under a row of a wallet's Transactions tab (the hash first opens a short explanation in the list), and from the Funding tx and Latest tx buttons of Wallet Flow.
Signals
| Signal | When it shows |
|---|---|
| This transaction failed | The transaction reverted; the reason is shown when the explorer gives one. The fee was still paid. |
| EIP-7702 delegation | A type 4 transaction set an account's code to a delegate contract, which can then act for the account. A known drainer is marked as such; a cleared delegation is shown as removed. |
| Unlimited token approval | The input approves a spender for an amount nobody runs out of (an ERC-20 approve or a Permit2 approval). |
| Approval for a whole NFT collection | setApprovalForAll lets an operator move every NFT of the collection the wallet holds. |
| Look-alike addresses | Two addresses in the transaction start and end with the same characters, the pattern address poisoning relies on. |
| Zero-value token transfer | A token transfer of 0, a common way to plant a look-alike address in a wallet's history. |
| Token flagged as spam | A token is marked as spam by Blockscout or carries a link or claim text in its name. |
Facts, not a verdict
Signals describe what the transaction contains. They are not a security review, and a transaction without signals is not vouched for.
Names and prices
- Names come from the zkCodex app catalog and each network's native bridges first, then the explorer's own tags, then the token a contract issues, and last a Blockscout Metadata name tag (such as an exchange hot wallet) for addresses still without a name, also on networks Blockscout does not index.
- Sender and recipient are labelled Wallet, Wallet (EIP-7702), Contract or Smart account from one read of their code.
- Token names and symbols, explorer tags, decoded arguments and revert reasons are written by whoever deployed or called the contract. Any web address in them is shown broken, such as claim-site[.]xyz or hxxps://, on the page and its share card, so none reads as a link from zkCodex. Wallet names such as alice.base.eth stay as they are.
- USD values use the native coin's price on the transaction's day from the price table XP uses; where that day is missing, Blockscout's rate at the time. Without either, only the coin amount is shown.
Data and freshness
SourceBlockscout where it serves the network, Etherscan elsewhere; the network's public node for a transaction no explorer has yet
Final transactionsOlder than 15 minutes: read once and kept for good, because a final transaction never changes
Recent and pendingRead again within seconds; press Check again on a pending transaction. The page itself renders again within two minutes of a visit until the transaction is final
Unknown hashesOne explorer call and one call to the network's node; the page is kept for a minute only, since a just-sent transaction can show up any moment
LimitsOne visitor can open about 40 transaction and contract pages a minute. These pages share a daily explorer allowance with the other public lookups; while it is used up, a page shows what is cached and asks again a few minutes later
Search enginesTransaction pages are not indexed, like wallet pages; shared links show a card with the summary