pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,370,915
← previous block
next block →
recent activity
Analyzing
Block #85,370,915
13 transactions · 11 stateful · 2026-07-03 17:13:01 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,370,915
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x6a47ee14
#4
0x5a5d9a99
#5
execOrder
#6
updatePosition
#7
0xed82b078
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
setData
#11
execOrders
#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
0x0da39371…1ecd
0x34b655…2a6f
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x161014f7…6f03
0x34b655…2a6f
2 touches
0 conflicts
0x2ad29b13…92e0
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x3e6302c8…64f5
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