How to..
Lookup Abi with Raw Data

ABI Lookup using raw data


The raw data of each transaction contains information about the function that is called. The first 10 characters (4 bytes) of this data represent a hash of the function's signature, known as the "method ID".

Emitted events also include this method ID, but in the form of the first topic (topic0) in the event's log data.


To decode the original arguments of a function call or event, the ABI (Application Binary Interface) for the function or event must be known. There are two ways to look up the ABI for a given method ID:

b32: This is a specialized collection of method and event ABIs that can be queried by method ID. The lookup is available at{{SIGNATURE}}.json This is a more general lookup proxy that can be used for method IDs that are not found in b32. It will also query public Ethereum databases if no match is found. The lookup is available at{{SIGNATURE}}

See more details on (opens in a new tab)


Transaction Example (opens in a new tab)

Function Example

The raw data of the first clause is


The first 10 characters (4 bytes) represent the method ID:


ABI Lookup links:

Event Example

The topics of the event log are:

[0] 0xec7c88986ebe0008ab11b3856b7e7963a907c417a7e0362bd682d2c08cb68d69
[1] 0x0000000000000000000000000000000000000000000000000000000000000002
[2] 0x03c98026ce7bf4163ff0e6baf409a11eb84b5e0820efceca8713c1fabd7dcd64
[3] 0x636e2e762a1dc36d0016729794476dc656182b44bb6ed8d1fcaf11c6098efcaa

The first topic, topic0, is the method ID of the event:


ABI Lookup links: