pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,920,402
57 transactions · 48 stateful · 2026-05-16 07:15:27 UTC
Parallelism
82/100
Blocked
69%
Avg conflicts / tx
2.12
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,920,402 · 57 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w16w27w38w010w112w014w315w416w117w220w236w539w643w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x3d181a38…936c
0xd32edf…ff58
11 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity