pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,151
58 transactions · 42 stateful · 2026-05-04 02:07:58 UTC
Parallelism
86/100
Blocked
60%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,283,151 · 58 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
1w03w14w05w17w010w011w012w113w015w219w020w122w124w025w135w236w337w438w541w145w149w250w352w457w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x249f7ccd…8b9e
0xd32edf…ff58
13 touches
21 conflicts
0xbad68552…e6bf
0x34b655…2a6f
12 touches
15 conflicts
0x24968e6d…0132
0x065c9d…c394
10 touches
10 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x3254d19b…f714
0x34b655…2a6f
8 touches
6 conflicts
0x414e9446…4b59
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
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
21 conflicts on slot 0x249f7ccd32…338b9e
Audit this contract →
← previous block·next block →recent activity