pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,095,318
41 transactions · 35 stateful · 2026-04-28 14:07:38 UTC
Parallelism
76/100
Blocked
51%
Avg conflicts / tx
1.2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #71,095,318 · 41 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
1w03w05w19w010w111w214w015w016w117w218w320w421w522w623w124w132w239w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x1c913164…5c2e
0x34b655…2a6f
10 touches
10 conflicts
0x9d651568…2c87
0x34b655…2a6f
8 touches
6 conflicts
0x23951077…539b
0x34b655…2a6f
8 touches
6 conflicts
0x49f231bb…c1c2
0x34b655…2a6f
6 touches
3 conflicts
0x5d845038…9777
0x34b655…2a6f
6 touches
3 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
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: 0x34b6552d…112a6f
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity