pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,086,549
← previous block
next block →
recent activity
Analyzing
Block #96,086,549
10 transactions · 9 stateful · 2026-08-15 02:40:05 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,086,549
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactInputSingle
#2
execOrders
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc371f5e…0955
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0x14e41c73…8244
0x34b655…2a6f
2 touches
0 conflicts
0x1e04ad1e…c417
0x34b655…2a6f
2 touches
0 conflicts
0x2021fb2a…d63b
0x34b655…2a6f
2 touches
0 conflicts
0x2ad29b13…92e0
0x34b655…2a6f
2 touches
0 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:
Perpl
1 conflict on slot
0xfc371f5ead…b30955
Audit this contract →
← previous block
·
next block →
recent activity