Practical overview
When it fits
Use it when a Python workflow needs to interpret Ethereum transaction input and the relevant contract ABI is available.
Who it is for
- Python developers building Ethereum contract analysis tools.
- Developers inspecting decoded arguments from transaction calldata.
- Developers examining constructor parameters in contract deployment input.
Documented uses
- Turn function-call transaction input into named, typed argument values.
- Decode constructor arguments using a contract ABI.
- Reuse an ABI-bound InputDecoder for repeated function-input decoding.
Requirements & limits
The project documents installation with pip and links to a Replit quick-start. Its repository lists an MIT license.
- Decoding depends on having the contract ABI; the README demonstrates fetching an ABI from Etherscan with an API key.
- The documented API accepts transaction input as a string or bytes and returns type-name-value tuples.
- The README describes the decoder as offline; an external ABI lookup is a separate step in its example.
- InputDecoder is offered for repeated decoding associated with one contract ABI.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install the Python package
Add WEB3 Input Decoder to a Python environment before using its documented decoding functions.
Before you start
- A Python environment with pip.
Steps
Run the command below.
pip install web3-input-decoderImport
decode_functionanddecode_constructorfromweb3_input_decoder.
Expected outcome
The package is installed and its documented decoding functions can be imported.
Guide limitations
- This covers installation and imports only; decoding requires transaction input and the relevant contract ABI.
Decode function or constructor input
Use a contract ABI and transaction input with the corresponding documented decoder.
Before you start
- The package installed in a Python environment.
- A contract ABI and transaction input data.
- For constructor decoding, deployed contract bytecode may be supplied separately when the input includes bytecode.
Steps
Import
decode_functionanddecode_constructorfromweb3_input_decoder.Pass the ABI and transaction input to
decode_functionfor a function call.Pass the ABI and constructor input to
decode_constructor; provide the optional bytecode argument when applicable.
Expected outcome
The documented functions return decoded type-name-value tuples.
Guide limitations
- The decoder needs the relevant ABI; the README's example retrieves one through the Etherscan API using an API key.
- This workflow decodes input data and does not document sending transactions.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- kigawas/web3-input-decoder · Official homepage title · retained in its source language

