pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,284,691
52 transactions · 33 stateful · 2026-05-04 02:18:20 UTC
Parallelism
77/100
Blocked
73%
Avg conflicts / tx
1.63
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,284,691 · 52 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w09w014w017w118w119w220w321w122w433w234w335w436w542w243w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x7566dd08…2187
0xd32edf…ff58
11 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0xc6a8c250…7379
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x02bfdbf9…6514
0x34b655…2a6f
8 touches
6 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: 0x34b6552d…112a6f
28 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity