pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,856,156
55 transactions · 44 stateful · 2026-05-06 17:47:09 UTC
Parallelism
73/100
Blocked
68%
Avg conflicts / tx
3.33
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #72,856,156 · 55 txs across 15 waves · depth 15
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
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1325w1427w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ad4e7e4…e466
0xd32edf…ff58
29 touches
105 conflicts
0x3638e1ad…ec0e
0x34b655…2a6f
24 touches
66 conflicts
0x908d4442…2c4b
0x34b655…2a6f
24 touches
66 conflicts
0x9b0235a2…a1dc
0x34b655…2a6f
24 touches
66 conflicts
0xac8e97a0…8426
0x34b655…2a6f
24 touches
66 conflicts
0xecd3dd4f…0f84
0x34b655…2a6f
24 touches
66 conflicts
0xf853eb8e…4027
0x34b655…2a6f
24 touches
66 conflicts
0xc6417de0…2191
0xc8689a…ee79
24 touches
66 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
105 conflicts on slot 0x9ad4e7e4fb…02e466
Audit this contract →
← previous block·next block →recent activity