pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,507,009
56 transactions · 44 stateful · 2026-05-09 17:58:10 UTC
Parallelism
68/100
Blocked
80%
Avg conflicts / tx
2.48
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #73,507,009 · 56 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w111w012w113w214w315w416w519w135w237w238w339w440w541w342w643w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x57de3828…3fbb
0x34b655…2a6f
14 touches
21 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
14 touches
21 conflicts
0x868859b9…3db5
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
14 touches
21 conflicts
0xc6417de0…2191
0xc8689a…ee79
12 touches
15 conflicts
0x5728edaf…f1d4
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity