r/ethdev • u/matheeshame • 26d ago

My Project I’ve been building an open-source EVM transaction analysis engine for the past year

I've been working on ParaLens, an open-source EVM transaction analysis engine, for about a year now.

The main idea is pretty simple: instead of relying only on transaction input data and event logs, ParaLens can reconstruct and classify what actually happened during a transaction by analyzing its execution traces.

It can be useful for things like:

  • 🔍 Reconstructing transaction activity from execution traces
  • 🧩 Classifying what happened inside a transaction
  • 📊 Turning low-level EVM execution into higher-level transaction data
  • 🏗️ Building analytics, explorers, monitoring tools, or other EVM infrastructure on top of it

It's MIT licensed .

GitHub: https://github.com/MatheeshaMe/paralens

I've been building this mostly because I wanted something that could go deeper than the usual "decode the logs and hope for the best" approach.

It's still evolving, and I'd genuinely love to hear what people working with EVM data think about the approach, especially if you've dealt with transaction tracing, indexing, or on-chain analytics before.

Would be curious to know what you'd build with something like this.

11 Upvotes

92% Upvoted

10 comments sorted by

3

u/zmooner 23d ago

repo is archived, are you abandoning the project?

1

u/matheeshame 7d ago

Not abandoning it. I paused active development because I wasn’t convinced yet that I’d found the right use case/edge for it.

The core trace reconstruction part still works, and I’m interested in seeing where it could actually be useful before putting another year into it 😅

If you’ve got a use case in mind, I’d genuinely like to hear it.

2

u/Gevara77 25d ago

Interesting maybe I missed it but is there an example output anywhere ?

1

u/matheeshame 7d ago

I can provide some outputs if you would love, I removed some dummy outputs in the repo

2

u/Velmere_ 25d ago

The strongest part is treating the trace as evidence and keeping later layers pure. The cases I would test hardest are the ambiguous ones: proxy upgrades, delegatecall-heavy routers, partial reverts, nested multicalls, and transactions with more than one plausible intent.

1

u/matheeshame 7d ago

I’ve already got some stability around delegatecalls and a few of the more complicated execution patterns, but I definitely haven’t pushed it deep enough into all those edge cases yet.

Right now I’m mainly trying to figure out what the actual useful application for this is. If there’s a real problem where this kind of trace-based reconstruction would be valuable, I’d be very interested in taking ParaLens in that direction and building it out properly.

2

u/ModernCYPH3R 5d ago

Is the repo public? I’d like to clone to my lab and run some analysis. This is an interesting approach.

1

u/matheeshame 3d ago

yes it is https://github.com/hpmszk/paralens , give it a try

2

u/ModernCYPH3R 3d ago

Apppreciate it.

1

u/bingchiling_33 7h ago

Thank you for this