pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,555,825
47 transactions · 37 stateful · 2026-05-14 14:40:29 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.64
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,555,825 · 47 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
1w02w13w04w15w06w110w219w020w121w223w424w526w727w828w935w236w340w242w445w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc6417de0…2191
0xc8689a…ee79
14 touches
21 conflicts
0x5c074a38…c1d3
0x34b655…2a6f
10 touches
10 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
10 touches
10 conflicts
0x9be2b99a…a959
0x34b655…2a6f
10 touches
10 conflicts
0x0711ec2d…d973
0x34b655…2a6f
10 touches
10 conflicts
0x4381471a…9ac1
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity