pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,288,217
39 transactions · 34 stateful · 2026-05-04 02:42:04 UTC
Parallelism
74/100
Blocked
74%
Avg conflicts / tx
1.95
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,288,217 · 39 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w18w29w110w311w113w414w225w526w627w728w333w434w5
- 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
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
10 touches
10 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
10 touches
10 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
10 touches
10 conflicts
0x9be2b99a…a959
0x34b655…2a6f
10 touches
10 conflicts
0x9cc607d0…c9c7
0x34b655…2a6f
10 touches
10 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