OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Developer Tools

EVM Abi Decoder

EVM Abi Decoder is a Java library that decodes raw EVM transaction input and contract log events using a contract's ABI definition in JSON format, returning data that an application can process.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

EVM Abi Decoder — OpenViST project profile in Developer Tools.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when a Java application has EVM transaction input or log data and the matching contract ABI, and needs to interpret that data in code.

Who it is for

  • Java developers building blockchain analytics or transaction-inspection applications.
  • Teams processing contract calls or event logs in EVM data pipelines.

Documented uses

  • Interpret raw transaction call data as a function name and parameter values.
  • Decode contract event logs using the relevant ABI.
  • Convert encoded EVM data into a processable representation for an application.
Before you choose

Requirements & limits

The public GitHub repository specifies the GPL-3.0 license. The README documents Maven dependency coordinates at version 0.1.6.

  • Decoding requires the applicable contract ABI in JSON format.
  • The library is Java-based and is integrated into an application rather than used as a standalone interface.
  • The README describes the API as 0.x.
  • The library uses slf4j-api without packaging a logging implementation, leaving the application to supply one.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Decode a transaction call with an ABI JSON file

Use the documented Java flow to obtain a decoded function call from raw transaction input.

Before you start

  • The EVM ABI Decoder Java library
  • A contract ABI in JSON format available as a resource
  • Raw EVM transaction input data

Steps

  1. Load the contract ABI JSON file into an AbiDecoder instance.

  2. Pass the raw transaction input string to decodeFunctionCall.

  3. Read the decoded function name and parameter values from the returned call.

Expected outcome

A DecodedFunctionCall representation, illustrated with a Uniswap V2 router swap and decoded parameter values.

Guide limitations

  • The decoded interpretation depends on the relevant contract ABI.
  • The example demonstrates transaction input decoding; it does not document a complete transaction-fetching workflow.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
osslabz/evm-abi-decoder · Official homepage title · retained in its source language
How we review sourcesSuggest a correction