pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,451,139
← previous block
next block →
recent activity
Analyzing
Block #86,451,139
15 transactions · 12 stateful · 2026-07-08 17:17:02 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,451,139
· 15 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
execPerpOps
#3
execPerpOps
#4
execFwdPositionOps
#5
executeBatch
#6
0x3f5c179b
#7
0xee83e0a5
#8
execFwdPositionOps
#9
0x6a4e8685
#10
setData
#11
0x835fa1…92a4
#12
0x195540…f365
#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
0x087ba8bb…f0f3
0x34b655…2a6f
2 touches
0 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
2 touches
0 conflicts
0x107b89e4…470d
0x34b655…2a6f
2 touches
0 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
2 touches
0 conflicts
0x6c5147d0…2f5b
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