pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,797,286
← previous block
next block →
recent activity
Analyzing
Block #95,797,286
9 transactions · 8 stateful · 2026-08-14 02:24:38 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,797,286
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
placeAndExecuteMarketBuy
· blocks 2
#5
swap
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x6a7e7cde
#3
placeAndExecuteMarketBuy
· blocks 1
#4
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xb71a8e04…7da5
0x065c9d…c394
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0xe0e73193…1287
0x000000…012a
2 touches
0 conflicts
0x7a46f55d…bb20
0x065c9d…c394
2 touches
0 conflicts
0x057ac2ab…400e
0x188d58…ea8e
2 touches
0 conflicts
0x057ac2ab…400f
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)
3 conflicts on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity