pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,684,885
← previous block
next block →
recent activity
Analyzing
Block #86,684,885
12 transactions · 9 stateful · 2026-07-09 19:21:57 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,684,885
· 12 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execFwdPositionOps
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#9
0x8a2e4e…96dd
#10
0x97950f…f5f5
#11
0xb8024e67
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
0x5554dc07…354b
0x34b655…2a6f
2 touches
0 conflicts
0x616c7c23…14e7
0x34b655…2a6f
2 touches
0 conflicts
0x9fd372a1…a959
0x34b655…2a6f
2 touches
0 conflicts
0xa1e228bc…b93c
0x34b655…2a6f
2 touches
0 conflicts
0xa3d14866…f3e2
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