pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,765,402
50 transactions · 38 stateful · 2026-05-15 14:01:13 UTC
Parallelism
74/100
Blocked
74%
Avg conflicts / tx
2.02
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,765,402 · 50 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
1w02w03w15w19w211w212w313w414w222w330w431w532w633w735w836w937w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xbce635aa…772e
0xd32edf…ff58
15 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
10 touches
10 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x388e001a…7e04
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