pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,193,667
← previous block
next block →
recent activity
Analyzing
Block #95,193,667
9 transactions · 7 stateful · 2026-08-11 23:33:57 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,193,667
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
executeBatch
#3
placeAndExecuteMarketSell
· blocks 2
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketSell
· blocks 1
#5
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
6 touches
3 conflicts
0xe55fc18e…8e67
0x40c49f…2af0
6 touches
3 conflicts
0x3cebc8f1…975c
0xe52b14…7230
2 touches
0 conflicts
0x58733c38…f2cd
0xe52b14…7230
2 touches
0 conflicts
0x693b762e…1fcd
0xe52b14…7230
2 touches
0 conflicts
0x6a3749da…c493
0xe52b14…7230
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