pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,284,717
35 transactions · 27 stateful · 2026-05-04 02:18:30 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
1.49
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #72,284,717 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w19w110w213w014w115w216w317w418w219w320w421w531w532w633w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1da4ad9b…08e1
0xd32edf…ff58
11 touches
15 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x6423fcab…a7c1
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xf853eb8e…4027
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: 0xd32edf66…9fff58
15 conflicts on slot 0x1da4ad9b89…cc08e1
Audit this contract →
← previous block·next block →recent activity