pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,429,341
34 transactions · 28 stateful · 2026-05-04 18:22:41 UTC
Parallelism
65/100
Blocked
79%
Avg conflicts / tx
2.62
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,429,341 · 34 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w29w010w111w212w313w214w315w416w517w618w719w820w923w124w225w226w330w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
12 touches
15 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
10 touches
10 conflicts
0xf22dac61…b0ae
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0xe1fd24a0…eaa6
0x34b655…2a6f
10 touches
10 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
8 touches
6 conflicts
0x8fcdf82f…961d
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity