pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,186,432
← previous block
next block →
recent activity
Analyzing
Block #97,186,432
10 transactions · 7 stateful · 2026-08-18 23:05:27 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,186,432
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
· blocks 1
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
placeAndExecuteMarketBuy
#9
setData
#3
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eff0903…8165
0x754704…b603
4 touches
1 conflict
0x777c9106…162a
0x754704…b603
4 touches
1 conflict
0x68c08dd2…be14
0x99c7a7…8bf0
4 touches
1 conflict
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x00532bf5…5711
0x754704…b603
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001a
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002a
0x1b6862…e19c
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
0x0eff0903c4…758165
Audit this contract →
← previous block
·
next block →
recent activity