pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,610,103
← previous block
next block →
recent activity
Analyzing
Block #86,610,103
16 transactions · 11 stateful · 2026-07-09 11:01:16 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,610,103
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
execPerpOps
#4
execPerpOps
#5
multicall
#6
updateDataFeedsValuesPartial
#7
withdraw
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
execOrders
#12
0x6a4f7ff4
#13
setData
#14
0x4677a8…2bf4
#15
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0009
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…000c
0x023eb9…b2b4
2 touches
0 conflicts
0x52a42b68…7c30
0x023eb9…b2b4
2 touches
0 conflicts
0x7e91b868…f17f
0x023eb9…b2b4
2 touches
0 conflicts
0x95e53961…16f0
0x023eb9…b2b4
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.
← previous block
·
next block →
recent activity