pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,319,383
75 transactions · 52 stateful · 2026-05-13 12:22:20 UTC
Parallelism
77/100
Blocked
75%
Avg conflicts / tx
2.48
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #74,319,383 · 75 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w17w08w111w212w217w319w220w321w422w523w660w764w966w1067w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
26 touches
78 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
26 touches
78 conflicts
0x13023f15…3eb2
0x34b655…2a6f
24 touches
66 conflicts
0xc6417de0…2191
0xc8689a…ee79
22 touches
55 conflicts
0xedb848fe…6534
0x34b655…2a6f
18 touches
36 conflicts
0x9be2b99a…a959
0x34b655…2a6f
16 touches
28 conflicts
0x57de3828…3fbb
0x34b655…2a6f
16 touches
28 conflicts
0x8db1e0f2…2fcf
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
78 conflicts on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity