pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,056,321
← previous block
next block →
recent activity
Analyzing
Block #86,056,321
10 transactions · 8 stateful · 2026-07-06 21:20:46 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,056,321
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
repayBorrow
#2
0x39435dac
#3
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0xed82b078
#7
setData
#8
modifyLiquidities
#9
0xc7e3ec2c
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0x562a4a30…f8d5
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x14682578…49e9
0x34b655…2a6f
2 touches
0 conflicts
0x59dbc306…f976
0x34b655…2a6f
2 touches
0 conflicts
0xec0e0220…cb90
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
0xd800e635bc…14b1d7
Audit this contract →
← previous block
·
next block →
recent activity