pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,095,411
53 transactions · 37 stateful · 2026-04-28 14:08:15 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
2.02
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #71,095,411 · 53 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w48w59w623w731w832w936w1037w1138w1239w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9abfa603…905e
0xd32edf…ff58
27 touches
91 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x11f25e19…8bb1
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x1d731f70…4557
0x34b655…2a6f
4 touches
1 conflict
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 0x9abfa603ae…6b905e
Audit this contract →
← previous block·next block →recent activity