pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,429,104
38 transactions · 26 stateful · 2026-05-04 18:21:07 UTC
Parallelism
53/100
Blocked
73%
Avg conflicts / tx
4.16
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #72,429,104 · 38 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1324w1428w1530w1634w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51f07e5b…9333
0xd32edf…ff58
35 touches
153 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0002
0x63e48b…53f2
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
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
153 conflicts on slot 0x51f07e5b0d…c79333
Audit this contract →
← previous block·next block →recent activity