pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,902,795
← previous block
next block →
recent activity
Analyzing
Block #95,902,795
12 transactions · 11 stateful · 2026-08-14 11:15:31 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,902,795
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
execOrder
#4
execOrder
· blocks 1
#6
execOrder
#7
execOrders
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
executeBatch
#11
setData
#2
matchOrders
#5
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe20cfb89…cd07
0x754704…b603
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0x34f4535c…bd3a
0x8f415d…5241
4 touches
1 conflict
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xef712f4a…0853
0x99c7a7…8bf0
4 touches
1 conflict
0x0f6aef87…8137
0x34b655…2a6f
2 touches
0 conflicts
0x431fa96d…6ac0
0x754704…b603
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
0xe20cfb8920…afcd07
Audit this contract →
← previous block
·
next block →
recent activity