pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,854,513
← previous block
next block →
recent activity
Analyzing
Block #95,854,513
9 transactions · 9 stateful · 2026-08-14 07:12:30 UTC
Parallelism
56
/100
Blocked
44
%
Avg conflicts / tx
0.78
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,854,513
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrder
· blocks 1
#2
placeAndExecuteMarketBuy
· blocks 3
#7
updateDataFeedsValuesPartial
#8
setData
#3
placeAndExecuteMarketBuy
· blocks 2
#6
execFwdPositionOpsV2
#4
placeAndExecuteMarketBuy
· blocks 1
#5
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
5
w3
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9df1da01…2074
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x3040553c…5e28
0x754704…b603
4 touches
1 conflict
0x3d9eb674…b3fb
0x754704…b603
4 touches
1 conflict
0x54474915…9e0b
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf35f8153…638b
0x754704…b603
4 touches
1 conflict
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:
Kuru Exchange: Market-MON/USDC
6 conflicts on slot
0x9df1da011c…6c2074
Audit this contract →
← previous block
·
next block →
recent activity