pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,745,469
← previous block
next block →
recent activity
Analyzing
Block #95,745,469
11 transactions · 9 stateful · 2026-08-13 22:04:02 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
#95,745,469
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
#2
execFwdPositionOpsV2
#3
0xb2d4797b
#4
placeAndExecuteMarketSell
#5
0x94defb17
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
transfer
#10
setData
#6
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf654f7e0…f2bd
0x968279…9342
4 touches
1 conflict
0x521a5982…a82a
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x6542c82c…2dee
0x968279…9342
4 touches
1 conflict
0x6542c82c…2def
0x968279…9342
4 touches
1 conflict
0x6542c82c…2df2
0x968279…9342
4 touches
1 conflict
0x6542c82c…2df3
0x968279…9342
4 touches
1 conflict
0x6542c82c…2df5
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
0xf654f7e01d…ebf2bd
Audit this contract →
← previous block
·
next block →
recent activity