pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,334,162
29 transactions · 24 stateful · 2026-05-13 14:00:35 UTC
Parallelism
55/100
Blocked
63%
Avg conflicts / tx
2.62
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,334,162 · 29 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w010w111w212w013w114w215w316w417w518w619w720w821w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
20 touches
45 conflicts
0xc6417de0…2191
0xc8689a…ee79
18 touches
36 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
18 touches
36 conflicts
0x908d4442…2c4b
0x34b655…2a6f
18 touches
36 conflicts
0x99f080dc…58c1
0x34b655…2a6f
18 touches
36 conflicts
0x9be2b99a…a959
0x34b655…2a6f
18 touches
36 conflicts
0xd6e02140…b2b5
0x34b655…2a6f
16 touches
28 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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity