pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,597,661
47 transactions · 34 stateful · 2026-05-10 04:00:24 UTC
Parallelism
79/100
Blocked
62%
Avg conflicts / tx
1.55
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,597,661 · 47 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
1w02w03w05w16w07w19w110w211w012w213w315w516w622w634w135w236w337w738w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08582262…44cc
0xd32edf…ff58
13 touches
21 conflicts
0xc13c1093…9a9d
0x754704…b603
12 touches
15 conflicts
0xc1ceff4b…04a0
0x3bd359…433a
12 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
8 touches
6 conflicts
0x00f7e3b7…e016
0x188d58…ea8e
8 touches
6 conflicts
0x8240d70c…7c3b
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
21 conflicts on slot 0x0858226259…0944cc
Audit this contract →
← previous block·next block →recent activity