pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,975,991
37 transactions · 29 stateful · 2026-05-07 07:04:43 UTC
Parallelism
73/100
Blocked
59%
Avg conflicts / tx
1.43
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,975,991 · 37 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
1w05w07w110w112w013w115w217w322w223w324w425w526w629w732w833w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
14 touches
21 conflicts
0x228f3bb1…ddbe
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xdaca243a…f9de
0x34b655…2a6f
8 touches
6 conflicts
0x6af306bb…2e81
0x3bd359…433a
8 touches
6 conflicts
0x150af51d…9c42
0x34b655…2a6f
6 touches
3 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
6 touches
3 conflicts
0x27132f04…5caa
0x34b655…2a6f
6 touches
3 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: 0x065c9d28…a9c394
21 conflicts on slot 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity