pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,906,948
← previous block
next block →
recent activity
Analyzing
Block #86,906,948
13 transactions · 11 stateful · 2026-07-10 20:05:54 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,906,948
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x0c7abd22
#2
0x1a945f9c
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
executeBatch
#8
execFwdPositionOps
#9
0x3f5c179b
#10
setData
#11
0x15d126…db85
#12
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
0x207e7985…b608
0x1efe02…37d6
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x29871f90…45bb
0x34b655…2a6f
2 touches
0 conflicts
0x352852e1…e791
0x34b655…2a6f
2 touches
0 conflicts
0x44429a9b…771d
0x34b655…2a6f
2 touches
0 conflicts
0x454cdf57…aebc
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