pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,022,165
← previous block
next block →
recent activity
Analyzing
Block #95,022,165
9 transactions · 8 stateful · 2026-08-11 09:10:29 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,022,165
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execFwdPositionOps
#3
placeAndExecuteMarketSell
· blocks 1
#5
batchUpdate
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
setData
#4
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2478c84…6956
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x4df2af73…275a
0xd18b7e…414b
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x0e4000ee…afb9
0x34b655…2a6f
2 touches
0 conflicts
0x13c845ca…0bca
0x34b655…2a6f
2 touches
0 conflicts
0x2bea6eae…9f7b
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:
USDC (USDC)
1 conflict on slot
0xa2478c8415…006956
Audit this contract →
← previous block
·
next block →
recent activity