pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,035,172
62 transactions · 43 stateful · 2026-05-07 13:38:37 UTC
Parallelism
84/100
Blocked
65%
Avg conflicts / tx
1.77
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,035,172 · 62 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
1w05w16w07w28w19w210w312w330w435w546w549w751w653w854w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaccedde0…36dd
0xd32edf…ff58
15 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0xdaca243a…f9de
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x0b390c61…dc07
0x065c9d…c394
12 touches
15 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xaccedde098…7e36dd
Audit this contract →
← previous block·next block →recent activity