pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,944,836
← previous block
next block →
recent activity
Analyzing
Block #86,944,836
11 transactions · 10 stateful · 2026-07-11 00:19:03 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,944,836
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
updatePosition
#7
execFwdPositionOps
#8
0x6a518c6f
#9
setData
#10
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xcadf8b62…6261
0x34b655…2a6f
4 touches
1 conflict
0xb9369a89…39a2
0x34b655…2a6f
4 touches
1 conflict
0xefda3300…69b0
0x34b655…2a6f
4 touches
1 conflict
0xb9369a89…39a3
0x34b655…2a6f
4 touches
1 conflict
0xbca4de0c…577c
0x34b655…2a6f
4 touches
1 conflict
0xd85ce098…8d3e
0x34b655…2a6f
3 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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity