pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,165,120
← previous block
next block →
recent activity
Analyzing
Block #86,165,120
16 transactions · 14 stateful · 2026-07-07 09:26:45 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,165,120
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
0x3f5c179b
#9
0xed82b078
#10
execFwdPositionOps
#11
execFwdPositionOps
#12
0x6a4cc6cc
#13
setData
#14
execOrders
#15
0xc7e3ec2c
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…0002
0x04fdea…47d7
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x29c1a140…099f
0x34b655…2a6f
2 touches
0 conflicts
0x2b8ae238…b119
0x34b655…2a6f
2 touches
0 conflicts
0x2c2761c0…476e
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.
← previous block
·
next block →
recent activity