Transaction Hash Lookup

WHAT IT DOES

The Transaction Hash Lookup tool gives you a complete technical view of any Ethereum transaction. Enter a transaction hash and the app fetches the transaction details, receipt, and block data. It displays the status (success/failed/pending), block number, from and to addresses, value transferred, gas limit, effective gas price (from the receipt, not the tx cap), gas used, total transaction cost, nonce, input data (raw bytes), and a count of logs. Where the RPC supports it, the tool also attempts to fetch internal transactions using debug_traceTransaction with the callTracer. This is useful for developers debugging contract interactions, auditors reviewing transaction flow, and users who want to understand exactly what happened in a transaction without opening a full block explorer.

HOW TO USE

1. Select your network from the dropdown or connect your wallet to use its RPC endpoint.

2. Paste a transaction hash (0x...) into the input field.

3. Click "Lookup" to fetch and display the transaction data.

4. Review the details in the card below: status, block, from/to addresses, value, gas limit, effective gas price, gas used, transaction cost, nonce, input data, log count, and internal transaction summary.

5. Use the "Clear" button to reset the view and enter another hash.

ONE TECHNICAL SECTION

This tool combines data from multiple RPC calls to build a complete transaction profile. It first fetches the transaction object via getTransaction, which provides the core fields: from, to, value, gas limit, gas price, nonce, and input data. It then fetches the receipt via getTransactionReceipt, which provides the status, gas used, logs, and — critically — the effectiveGasPrice. Post-EIP-1559, tx.gasPrice is only the cap, not the actual price paid; using receipt.effectiveGasPrice gives the real cost. The tool calculates the total transaction cost as effectiveGasPrice * gasUsed and formats it in ETH. For internal transactions, it attempts to call debug_traceTransaction with the callTracer, which returns a structured tree of internal calls. The tool flattens this tree to count internal calls and sum any value transferred internally. If the tracer is not available, it gracefully falls back to showing "None (or tracer unsupported)." This combination gives you both the high-level summary and the low-level details of the transaction.

WHAT IT CANNOT SEE

This tool cannot decrypt transaction input data without the ABI — input data is shown as raw hex bytes, which are not human-readable without the contract's Application Binary Interface. It cannot view pending transactions in the mempool beyond basic existence; if a transaction is not yet mined, you will only see a "Pending" status and no receipt or logs. It cannot trace internal transactions on chains that do not support debug_traceTransaction, such as some L2s or providers that disable this method. The tool is limited by RPC archive node availability; older transactions may be missing if the provider does not store

PLEASE NOTE

Sites and services change over time and this app may need updating to match.