pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,233,767
50 transactions · 39 stateful · 2026-05-03 20:36:05 UTC
Parallelism
76/100
Blocked
64%
Avg conflicts / tx
1.84
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,233,767 · 50 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w19w010w112w213w314w021w022w123w224w325w434w435w536w637w739w841w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0151daf6…6154
0xd32edf…ff58
9 touches
10 conflicts
0x1c389468…6b0e
0x34b655…2a6f
8 touches
6 conflicts
0x005fb969…2d97
0x34b655…2a6f
8 touches
6 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
8 touches
6 conflicts
0x35b85d8e…1edd
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: 0x34b6552d…112a6f
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity