pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,267,293
72 transactions · 47 stateful · 2026-05-04 00:21:25 UTC
Parallelism
86/100
Blocked
68%
Avg conflicts / tx
1.43
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,267,293 · 72 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
1w07w110w011w012w014w016w018w120w222w323w124w025w127w233w137w038w139w240w341w451w552w153w654w758w861w963w365w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54a37fe5…b7ff
0xd32edf…ff58
19 touches
45 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x801a6e57…d85c
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x2877f440…c2c8
0x34b655…2a6f
8 touches
6 conflicts
0x3254d19b…f714
0x34b655…2a6f
8 touches
6 conflicts
0x3c35979a…975d
0x34b655…2a6f
8 touches
6 conflicts
0x65e795ca…0320
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
45 conflicts on slot 0x54a37fe520…41b7ff
Audit this contract →
← previous block·next block →recent activity