pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,498,711
68 transactions · 49 stateful · 2026-05-05 02:04:41 UTC
Parallelism
75/100
Blocked
71%
Avg conflicts / tx
2.74
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #72,498,711 · 68 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w28w112w313w217w319w351w252w453w554w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
32 touches
120 conflicts
0x3ac9e0f2…b632
0x34b655…2a6f
14 touches
21 conflicts
0x2484cc15…5afc
0x34b655…2a6f
12 touches
15 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
12 touches
15 conflicts
0x50c2960c…5f37
0x34b655…2a6f
12 touches
15 conflicts
0x6c042c61…f883
0x34b655…2a6f
12 touches
15 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
12 touches
15 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
12 touches
15 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
120 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity