pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,503,607
← previous block
next block →
recent activity
Analyzing
Block #86,503,607
15 transactions · 12 stateful · 2026-07-08 23:07:49 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,503,607
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xa96df62f
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#6
batchUpdate
#7
execFwdPositionOps
#8
0x6a4ed8bd
#9
0x99c9da…4473
#10
0x1d3dff…7276
#11
0xf12ce6…bdc0
#12
execOrders
#13
execOrders
#14
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
0x000aa119…0cb2
0x34b655…2a6f
2 touches
0 conflicts
0x278e9719…0d9f
0x34b655…2a6f
2 touches
0 conflicts
0x2b7950c1…2342
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 conflicts
0x64aaadbf…f9f3
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