pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,285,987
38 transactions · 27 stateful · 2026-05-04 02:27:04 UTC
Parallelism
58/100
Blocked
74%
Avg conflicts / tx
3.37
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #72,285,987 · 38 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w921w1022w1124w1227w1328w1431w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9ba4cbc…9a9f
0xd32edf…ff58
31 touches
120 conflicts
0xb6d6d740…e91a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
120 conflicts on slot 0xf9ba4cbc5f…179a9f
Audit this contract →
← previous block·next block →recent activity