pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,181,387
← previous block
next block →
recent activity
Analyzing
Block #85,181,387
13 transactions · 12 stateful · 2026-07-02 20:10:32 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
#85,181,387
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xab083028
#2
dagSwapByOrderId
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0xed82b078
#7
0x6df9e92b
#8
0x6a46c630
#9
setData
#10
execOrders
#11
execOrders
#12
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
0x0d614c32…4f1d
0x11ed3b…2c96
2 touches
0 conflicts
0x38aa1898…fdf5
0x11ed3b…2c96
2 touches
0 conflicts
0x3f1434d4…1ce1
0x11ed3b…2c96
2 touches
0 conflicts
0x3e98e7ac…698b
0x188d58…ea8e
2 touches
0 conflicts
0x3e98e7ac…698d
0x188d58…ea8e
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