pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,029,721
39 transactions · 31 stateful · 2026-05-07 13:02:19 UTC
Parallelism
77/100
Blocked
58%
Avg conflicts / tx
1.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,029,721 · 39 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
1w02w13w14w05w16w07w18w29w310w413w214w228w531w632w733w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
12 touches
15 conflicts
0x70b2f813…783c
0x2a68ba…90c5
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x0b390c61…dc07
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xb389d45f…8a4c
0x34b655…2a6f
8 touches
6 conflicts
0x1c3af45b…416e
0x6ca43f…c331
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: 0x065c9d28…a9c394
15 conflicts on slot 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity