pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,668,755
12 transactions · 10 stateful · 2026-05-15 03:15:55 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,668,755 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89292a99…c90e
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x1cc5411d…dda3
0x065c9d…c394
4 touches
1 conflict
0x407643e7…8a08
0x065c9d…c394
3 touches
1 conflict
0x2ae53206…7fed
0x065c9d…c394
3 touches
1 conflict
0xdbe0ce6e…c77d
0x065c9d…c394
3 touches
1 conflict
0x80cf36ec…ebd0
0x065c9d…c394
3 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
2 touches
0 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: 0x065c9d28…a9c394
1 conflict on slot 0x89292a9968…5fc90e
Audit this contract →
← previous block·next block →recent activity