pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,486,509
← previous block
next block →
recent activity
Analyzing
Block #86,486,509
13 transactions · 11 stateful · 2026-07-08 21:13:44 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,486,509
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5a5d9a99
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
forward
#8
0xed82b078
#9
execFwdPositionOps
#10
setData
#11
0xffd526…52db
#12
0x08d6dc…4ae0
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
0x01c969a3…227b
0x34b655…2a6f
2 touches
0 conflicts
0x0a49c44b…4b7f
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x51ffd098…59d4
0x34b655…2a6f
2 touches
0 conflicts
0x59dccbd8…2bf6
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