pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,720,471
← previous block
next block →
recent activity
Analyzing
Block #95,720,471
13 transactions · 11 stateful · 2026-08-13 19:58:19 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,720,471
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
execOrders
#5
0x5acec890
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
execFwdPositionOpsV2
#10
0x6a7e2253
#11
setData
#12
0x61d59c2d
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0x8ee86cb5…db9c
0x99c7a7…8bf0
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0xe20cfb89…cd07
0x754704…b603
4 touches
1 conflict
0x165e7cb7…e0eb
0x8f415d…5241
3 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
0x34b655…2a6f
2 touches
0 conflicts
0xc64614eb…0f3a
0x34b655…2a6f
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
0xdc255d2170…b4c377
Audit this contract →
← previous block
·
next block →
recent activity