pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,288,421
56 transactions · 45 stateful · 2026-05-04 02:43:25 UTC
Parallelism
86/100
Blocked
51%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,288,421 · 56 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w08w111w012w014w117w018w019w120w221w123w333w134w235w336w439w240w547w348w250w655w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x078495a9…89aa
0xd32edf…ff58
15 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
8 touches
6 conflicts
0x2877f440…c2c8
0x34b655…2a6f
8 touches
6 conflicts
0x3254d19b…f714
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x624a1f2a…3f9b
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
28 conflicts on slot 0x078495a9c6…a789aa
Audit this contract →
← previous block·next block →recent activity