pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,669,062
30 transactions · 21 stateful · 2026-05-10 11:59:42 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,669,062 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w08w09w110w111w013w015w016w118w019w122w123w224w325w427w028w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57d7c08f…250d
0xd32edf…ff58
9 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xa0dd011c…ef26
0x1b6862…e19c
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3108871…46d0
0x34b655…2a6f
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x1c354dc0…96de
0x754704…b603
6 touches
3 conflicts
0xf91b744e…9117
0x754704…b603
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
10 conflicts on slot 0x57d7c08f6c…06250d
Audit this contract →
← previous block·next block →recent activity