pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,948,693
← previous block
next block →
recent activity
Analyzing
Block #86,948,693
14 transactions · 11 stateful · 2026-07-11 00:44:48 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,948,693
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execPerpOps
#3
execPerpOps
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
#8
forward
#9
execFwdPositionOps
#10
0x6a519277
#11
setData
#13
execOrders
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x008accc4…1da7
0x34b655…2a6f
2 touches
0 conflicts
0x008accc4…1da8
0x34b655…2a6f
2 touches
0 conflicts
0x17a4cfb2…f39f
0x34b655…2a6f
2 touches
0 conflicts
0x216ffe66…1f94
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
0xa6b89ebbaf…5fa66e
Audit this contract →
← previous block
·
next block →
recent activity