pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,499,685
← previous block
next block →
recent activity
Analyzing
Block #86,499,685
15 transactions · 8 stateful · 2026-07-08 22:41:39 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,499,685
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execPerpOps
#3
execPerpOps
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
0x6a4ed29b
#9
transfer
#10
setData
#11
0x02ff47…d3c7
#12
0xb7dcb3…a23e
#13
0x61289d…e5ce
#14
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
0x0da39371…1ecd
0x34b655…2a6f
2 touches
0 conflicts
0x1ba17872…9dd9
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5317
0x34b655…2a6f
2 touches
0 conflicts
0x5e782d17…5318
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