pev.Parallel Execution Visualizer
offline
by Silk Nodes →Monad · Developer Tooling
Is your contract killing parallelism?
Paste a block number. pev reconstructs the execution graph, surfaces storage contention, and tells you exactly which slots are costing you throughput.
Latest analyzed block
#70,846,0947 txs · 0x757c0e8e…d27437
Parallelism
86/100
Blocked
0%
Waves
1
Conflicts
0
Clean, every transaction ran independently in 1 wave.
click to inspect →
Auditing your own contract? Paste its address in the search above to see its parallelism profile.
Recent activity
connecting
Three principles
01
Clarity before aesthetics.
The design defers to the data. Decoration exists only where it helps a developer see cause and effect faster.
02
Causality over summary.
A dashboard shows what is. pev shows what caused what. The brand should feel investigative, not reportorial.
03
Technical, but literate.
Monospace for the truth, hashes, slots, gas. Serif for the voice. Sans for the interface. A three-voice system that stays distinct.
What we measure
Parallelism Score
Theoretical speedup vs. serial execution, on a 0-100 scale. Higher means the same work could finish in fewer rounds.
Execution Waves
Minimum number of sequential rounds the block needs because of storage conflicts. Lower is more parallel.
Hot Storage Slots
Storage slots touched by multiple txs in the same block, the bottlenecks.
What this is, and isn't
Every metric on this page is computed from real prestateTracer output. We show theoretical parallelism, the maximum speedup the block's conflict structure allows, not what Monad's scheduler actually decided. That's internal and not exposed via RPC, so we don't fake it. Method names are decoded via the 4byte directory when a selector has been submitted there; otherwise we show the raw 4-byte hex. Contract names come from Sourcify when verified, coverage on Monad mainnet is still early.