pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,023,066
← previous block
next block →
recent activity
Analyzing
Block #96,023,066
11 transactions · 9 stateful · 2026-08-14 21:20:45 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,023,066
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
0x94defb17
· blocks 1
#9
0xd67b8ed4
#10
setData
#8
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fc3cf50…23cb
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x25e5e130…d407
0x968279…9342
4 touches
1 conflict
0x25e5e130…d408
0x968279…9342
4 touches
1 conflict
0x25e5e130…d40a
0x968279…9342
4 touches
1 conflict
0x6fc3cf50…23c5
0x968279…9342
4 touches
1 conflict
0x6fc3cf50…23c6
0x968279…9342
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:
0x96827978…f09342
1 conflict on slot
0x6fc3cf50fd…1723cb
Audit this contract →
← previous block
·
next block →
recent activity