Dune turns encoded smart contract logs into readable event names and parameter values using ABI-based decoding.
Decoded EVM smart contract events with readable names, parameters, and JSON payloads across 50+ chains. Dune turns encoded smart contract logs into readable event names and parameter values using ABI-based decoding.
Raw EVM logs are encoded: topic0 is a hashed event signature, indexed event parameters are stored in the remaining topics, and non-indexed parameters are packed into the data field. Dune matches those logs to ABIs and signatures so teams can read the event name and parameter names and values directly.
topic0 becomes the event signature and name, indexed topics become named parameters, and the data payload becomes decoded non-indexed values. Dune adds project namespaces and contract names, so analysts can query the result without rebuilding ABI pipelines themselves.
logs_decoded tables give broad decoded event coverage with event names, signatures, contract metadata, source transactions, and decoded_json payloads in one public table per chain. Specific decoded event tables, such as uniswap_v3_ethereum.UniswapV3Pool_evt_Swap, model each event as a table with typed columns. Both come from the same managed decoding capability.
Factory-deployed contracts, such as Uniswap V3 pools, roll up under the same Dune namespace and decoded table family. Instead of chasing implementation contracts, proxy patterns, or topic hashes one address at a time, teams analyze activity through readable events like swaps, mints, burns, and collects.
Decoded tables are updated within minutes of chain activity. They are free to query on Dune, and the same decoded event data is available via API or Datashare for warehouse delivery.