pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,853,832
← previous block
next block →
recent activity
Analyzing
Block #86,853,832
11 transactions · 8 stateful · 2026-07-10 14:10:38 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,853,832
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePosition
#2
execFwdPositionOps
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a50fdd6
#6
0xbcd337…a122
#7
setData
#8
0xb8024e48
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a3774a3…4de9
0x34b655…2a6f
4 touches
1 conflict
0x5d863b2f…bd28
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0ee13be7…7b2c
0x34b655…2a6f
4 touches
1 conflict
0x070503e7…4262
0x6657d1…8ccc
2 touches
0 conflicts
0x0d051036…403b
0x6657d1…8ccc
2 touches
0 conflicts
0x18936740…cbc4
0x6657d1…8ccc
2 touches
0 conflicts
0x21e33d7a…52fe
0x6657d1…8ccc
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0x5a3774a3a5…f54de9
Audit this contract →
← previous block
·
next block →
recent activity