pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,660,547
72 transactions · 42 stateful · 2026-05-10 11:02:12 UTC
Parallelism
81/100
Blocked
67%
Avg conflicts / tx
1.67
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,660,547 · 72 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w27w310w412w515w521w650w651w752w853w954w1055w1157w1262w1364w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f5cb878…0eb4
0xd32edf…ff58
27 touches
91 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0xf2438038…5fa7
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
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
91 conflicts on slot 0x1f5cb87812…860eb4
Audit this contract →
← previous block·next block →recent activity