pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,513,360
← previous block
next block →
recent activity
Analyzing
Block #86,513,360
11 transactions · 9 stateful · 2026-07-09 00:12:50 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,513,360
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
exec
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#8
execFwdPositionOps
#9
0x6a4ee7fa
#10
setData
#7
depositCollateral
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8669ab5…6af7
0x754704…b603
4 touches
1 conflict
0xaf831072…51d5
0x80f006…d585
4 touches
1 conflict
0xaf831072…51d6
0x80f006…d585
4 touches
1 conflict
0x00000000…0036
0x386489…7508
4 touches
1 conflict
0xe069120c…952c
0x000000…012a
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x107b5402…dfc7
0x188d58…ea8e
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:
USDC (USDC)
1 conflict on slot
0xa8669ab582…bb6af7
Audit this contract →
← previous block
·
next block →
recent activity