pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,949,407
← previous block
next block →
recent activity
Analyzing
Block #86,949,407
11 transactions · 9 stateful · 2026-07-11 00:49:33 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,949,407
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
updatePriceFeedsIfNecessary
#7
updateDataFeedsValuesPartial
#8
setData
#9
0xb8024e4b
#10
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x216ffe66…1f94
0x34b655…2a6f
2 touches
0 conflicts
0x230a3fb0…e64c
0x34b655…2a6f
2 touches
0 conflicts
0x2979182b…a682
0x34b655…2a6f
2 touches
0 conflicts
0x5f676e75…f270
0x34b655…2a6f
2 touches
0 conflicts
0x94e7f277…471b
0x34b655…2a6f
2 touches
0 conflicts
0xbd9491f7…dd92
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0xac3e4969cf…1739e9
Audit this contract →
← previous block
·
next block →
recent activity