pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,651,518
81 transactions · 50 stateful · 2026-05-10 10:01:22 UTC
Parallelism
89/100
Blocked
70%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,651,518 · 81 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
1w02w04w05w06w17w012w114w015w117w118w219w021w022w126w236w237w339w446w569w280w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01dca5d2…c35b
0xd32edf…ff58
17 touches
36 conflicts
0xf2438038…5fa7
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xe6455d1f…1029
0x754704…b603
10 touches
10 conflicts
0x0d0b2509…074d
0x3bd359…433a
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0xe5e7089a…fb91
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
36 conflicts on slot 0x01dca5d2e1…72c35b
Audit this contract →
← previous block·next block →recent activity