pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,471
39 transactions · 29 stateful · 2026-05-04 02:10:08 UTC
Parallelism
56/100
Blocked
72%
Avg conflicts / tx
3.67
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #72,283,471 · 39 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1222w1225w1326w1427w1531w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f7bf60e…abbb
0xd32edf…ff58
33 touches
136 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x0f28fb99…3d29
0x1b6862…e19c
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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: 0xd32edf66…9fff58
136 conflicts on slot 0x2f7bf60e01…92abbb
Audit this contract →
← previous block·next block →recent activity