pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,965,630
← previous block
next block →
recent activity
Analyzing
Block #86,965,630
11 transactions · 11 stateful · 2026-07-11 02:37:59 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,965,630
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
forward
#7
execFwdPositionOps
#8
0x6a51acfe
#9
setData
#10
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc2d4622…e7e9
0x34b655…2a6f
4 touches
1 conflict
0xc03846bb…73b3
0x34b655…2a6f
4 touches
1 conflict
0xd2d3fe13…b827
0x34b655…2a6f
4 touches
1 conflict
0xd2d3fe13…b828
0x34b655…2a6f
4 touches
1 conflict
0x2b856d86…7988
0x34b655…2a6f
4 touches
1 conflict
0x2c413089…5bdf
0x34b655…2a6f
4 touches
1 conflict
0x3be33cca…0fff
0x34b655…2a6f
4 touches
1 conflict
0x3be33cca…1000
0x34b655…2a6f
4 touches
1 conflict
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
0xbc2d462244…49e7e9
Audit this contract →
← previous block
·
next block →
recent activity