pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,920,050
52 transactions · 33 stateful · 2026-05-16 07:13:06 UTC
Parallelism
83/100
Blocked
67%
Avg conflicts / tx
0.98
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,920,050 · 52 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w17w210w013w316w417w018w519w020w121w227w428w140w242w346w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0xc8f217cb…5d87
0xd32edf…ff58
7 touches
6 conflicts
0x69ee9e7d…d18b
0x065c9d…c394
7 touches
6 conflicts
0xebd2f809…3132
0x34b655…2a6f
6 touches
3 conflicts
0xfc04639a…4ab3
0x34b655…2a6f
6 touches
3 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: 0x34b6552d…112a6f
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity