pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,204,539
47 transactions · 43 stateful · 2026-05-08 08:25:32 UTC
Parallelism
49/100
Blocked
79%
Avg conflicts / tx
6.38
Longest chain
24 deep
Execution timeline
did this block parallelize well?
view
block #73,204,539 · 47 txs across 24 waves · depth 24
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w37w48w59w610w711w841w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6417de0…2191
0xc8689a…ee79
40 touches
190 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
38 touches
171 conflicts
0x5728edaf…f1d4
0x34b655…2a6f
34 touches
136 conflicts
0x578e7f66…1b56
0x34b655…2a6f
32 touches
120 conflicts
0x6b6dbe88…d7f7
0x34b655…2a6f
30 touches
105 conflicts
0x388e001a…7e04
0x34b655…2a6f
30 touches
105 conflicts
0x00000000…0002
0xab3526…fa38
18 touches
36 conflicts
0xa64da8fc…4630
0xd32edf…ff58
7 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: 0xc8689a47…62ee79
190 conflicts on slot 0xc6417de023…802191
Audit this contract →
← previous block·next block →recent activity