pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,914,713
36 transactions · 32 stateful · 2026-05-16 06:37:27 UTC
Parallelism
56/100
Blocked
72%
Avg conflicts / tx
3.11
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #74,914,713 · 36 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w28w39w410w511w112w013w114w215w316w417w518w625w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
22 touches
55 conflicts
0x7b97d40a…09ed
0x34b655…2a6f
18 touches
36 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x45b9e08c…a11b
0x34b655…2a6f
16 touches
28 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
16 touches
28 conflicts
0x9be2b99a…a959
0x34b655…2a6f
16 touches
28 conflicts
0xc6417de0…2191
0xc8689a…ee79
16 touches
28 conflicts
0x0711ec2d…d973
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 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity