pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,410,409
← previous block
next block →
recent activity
Analyzing
Block #91,410,409
11 transactions · 8 stateful · 2026-07-29 18:03:58 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,410,409
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
· blocks 1
#8
swapExactTokensForTokensSupportingFeeOnTransferTokens
#9
setData
#10
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c2fc330…0091
0x34b655…2a6f
4 touches
1 conflict
0x1110ff7d…d969
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00278f77…b731
0x34b655…2a6f
2 touches
0 conflicts
0x065b1661…9e03
0x34b655…2a6f
2 touches
0 conflicts
0x06711918…adfb
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x0a1643e3…e20d
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
0x9c2fc33042…7d0091
Audit this contract →
← previous block
·
next block →
recent activity