pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,663
75 transactions · 32 stateful · 2026-05-18 21:26:03 UTC
Parallelism
84/100
Blocked
72%
Avg conflicts / tx
1.24
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #75,478,663 · 75 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w18w210w216w223w325w330w449w550w051w152w254w355w468w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fe83fc0…f426
0xd32edf…ff58
23 touches
66 conflicts
0x846f2172…fd54
0x0555e3…2b9c
8 touches
6 conflicts
0x5086c64a…28ba
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x46cb45de…a566
0x188d58…ea8e
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x46cb45de…a567
0x188d58…ea8e
6 touches
3 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: 0xd32edf66…9fff58
66 conflicts on slot 0x4fe83fc094…a1f426
Audit this contract →
← previous block·next block →recent activity