pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,679,252
57 transactions · 46 stateful · 2026-05-10 13:08:35 UTC
Parallelism
63/100
Blocked
78%
Avg conflicts / tx
4.37
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #73,679,252 · 57 txs across 21 waves · depth 21
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
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w38w314w244w445w546w647w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
36 touches
153 conflicts
0xc6417de0…2191
0xc8689a…ee79
34 touches
136 conflicts
0x908d4442…2c4b
0x34b655…2a6f
32 touches
120 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
30 touches
105 conflicts
0xd84e22f4…ccfb
0x34b655…2a6f
24 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0xedb848fe…6534
0x34b655…2a6f
18 touches
36 conflicts
0x9be2b99a…a959
0x34b655…2a6f
18 touches
36 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
153 conflicts on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity