pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,288,122
35 transactions · 28 stateful · 2026-05-04 02:41:26 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.34
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,288,122 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w110w211w314w015w116w117w218w219w321w026w128w329w431w632w733w834w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xebf19faa…72cb
0x34b655…2a6f
8 touches
6 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
6 touches
3 conflicts
0xbb975a6c…bff4
0x34b655…2a6f
6 touches
3 conflicts
0x908d4442…2c4b
0x34b655…2a6f
6 touches
3 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
6 touches
3 conflicts
0x207c32d3…d39b
0x34b655…2a6f
6 touches
3 conflicts
0x2484cc15…5afc
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity