pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,267,331
52 transactions · 36 stateful · 2026-05-04 00:21:40 UTC
Parallelism
79/100
Blocked
67%
Avg conflicts / tx
1.21
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #72,267,331 · 52 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w29w011w312w013w122w433w534w637w141w542w643w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x764a6d19…1f42
0xd32edf…ff58
13 touches
21 conflicts
0x831f75b4…945d
0x34b655…2a6f
8 touches
6 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
6 touches
3 conflicts
0x51087f5a…61f7
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
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: 0x754704bc…afb603
21 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity