What tools does Now I See Web3 provide?

Now I See Web3 provides three core tools: Transaction Analyzer (decode any tx hash across chains), Calldata Decoder (decode raw calldata hex into function name and parameters), and Error Decoder (translate Solidity revert data into readable error messages).

Is Now I See Web3 free to use?

Yes. Now I See Web3 is completely free and open-source. No wallet connection, no API key, no account required. All operations are read-only.

What is Now I See Web3?

Now I See Web3 is a free, open-source on-chain data analyzer designed for Ethereum and EVM-compatible blockchain developers. The platform converts raw, unreadable on-chain data — hexadecimal calldata, encoded error responses, and transaction hashes — into clear, human-readable information.

Whether you are debugging a failed transaction, inspecting a smart contract call, or trying to understand what a transaction actually did on-chain, Now I See Web3 gives you the visibility you need without requiring you to manually decode ABI-encoded data or write custom scripts.

The Tools

Now I See Web3 provides three core tools, each focused on a specific aspect of on-chain data analysis:

Transaction Analyzer — Enter any transaction hash and select a network. The analyzer searches across multiple EVM chains in parallel and returns full transaction details, including decoded calldata and event logs. This is the fastest way to understand what happened in a transaction without opening a block explorer and manually tracing each step.
Calldata Decoder — Paste any raw calldata hex string and instantly see the decoded function name, parameter types, and values. This tool uses the 4Byte directory and ABI decoding to interpret the first four bytes as a function selector and decode the remaining bytes as ABI-encoded parameters.
Error Decoder — When a Solidity transaction reverts, the EVM returns encoded revert data. The Error Decoder translates this data into a readable error message, whether it is a standardError(string), a Panic(uint256) code, or a custom error defined in a contract ABI.

Developer Tool Only — No Financial Features

Now I See Web3 is strictly a developer debugging and inspection tool. It contains no cryptocurrency investment features, no payment processing, no token transfers, and no trading functionality of any kind. There is no wallet connection, no private key handling, no API key requirement, and no collection of personal data. All operations are read-only: the tools only read and decode data that already exists on public blockchains.

If you are looking for a platform to buy, sell, or transfer cryptocurrency, this is not it. Now I See Web3 exists solely to help developers understand what raw on-chain data means.

Why We Built This

Working with on-chain data is a fundamental part of Web3 development, but the raw data format — ABI-encoded hexadecimal strings — is designed for machines, not humans. Developers regularly encounter transaction hashes they cannot read, calldata they cannot interpret, and error messages that are completely opaque without the right tools.

Now I See Web3 was built to close that gap. The goal is simple: give Web3 developers a fast, reliable, and free tool that makes on-chain data immediately understandable. No setup, no wallet connection, no API keys. Just paste the data and see what it means.

Open Source

Now I See Web3 is fully open source. The source code is available on GitHub. Contributions, bug reports, and feature requests are welcome. If you find a bug or have an idea for improving the tools, please open an issue or submit a pull request.

The project is created and maintained by choi.eth, a blockchain developer specializing in EVM infrastructure and smart contract tooling. With hands-on experience building on Ethereum, Arbitrum, Optimism, and other OP Stack chains, choi.eth has worked extensively with ABI encoding, cross-chain messaging, and L2 withdrawal/deposit flows. Now I See Web3 was born from the daily frustration of manually decoding hex data during development and debugging — a problem every EVM developer faces but few tools solve well.