pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,648,989
25 transactions · 24 stateful · 2026-05-10 09:44:22 UTC
Parallelism
36/100
Blocked
67%
Avg conflicts / tx
4.08
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,648,989 · 25 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w310w411w512w613w714w815w916w1017w1118w1219w1320w1423w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6417de0…2191
0xc8689a…ee79
28 touches
91 conflicts
0xd49762c9…1359
0x34b655…2a6f
26 touches
78 conflicts
0xedb848fe…6534
0x34b655…2a6f
26 touches
78 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
18 touches
36 conflicts
0x0711ec2d…d973
0x34b655…2a6f
16 touches
28 conflicts
0x57de3828…3fbb
0x34b655…2a6f
16 touches
28 conflicts
0xee2bb5dd…99f2
0x34b655…2a6f
14 touches
21 conflicts
0xaed1fa0f…08fa
0x34b655…2a6f
10 touches
10 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xc8689a47…62ee79
91 conflicts on slot 0xc6417de023…802191
Audit this contract →
← previous block·next block →recent activity