pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,285,938
67 transactions · 48 stateful · 2026-05-04 02:26:45 UTC
Parallelism
75/100
Blocked
79%
Avg conflicts / tx
3.19
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #72,285,938 · 67 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
1w03w14w25w36w47w58w69w710w812w913w1014w1115w1216w1324w1438w1539w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x560c8553…0c64
0xd32edf…ff58
33 touches
136 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x1045386d…cb86
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0018
0x1b6862…e19c
12 touches
15 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 0x560c8553b3…ef0c64
Audit this contract →
← previous block·next block →recent activity