pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,536,599
← previous block
next block →
recent activity
Analyzing
Block #95,536,599
11 transactions · 10 stateful · 2026-08-13 04:32:26 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,536,599
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
placeAndExecuteMarketBuy
· blocks 1
#6
verifyOracleProofV2
#7
execFwdPositionOps
#8
transfer
#9
setData
#10
0x59558d29
#5
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ed0b378…9bc6
0xa6afd3…d132
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6a9d
0x2b46c0…1669
2 touches
0 conflicts
0xe2263bea…6aa0
0x2b46c0…1669
2 touches
0 conflicts
0xea8e47b0…abfe
0x2b46c0…1669
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:
Kuru Exchange: Market-WETH/USDC
1 conflict on slot
0x4ed0b3780e…469bc6
Audit this contract →
← previous block
·
next block →
recent activity