pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,431,772
← previous block
next block →
recent activity
Analyzing
Block #97,431,772
12 transactions · 11 stateful · 2026-08-19 20:11:20 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,431,772
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0xab083028
#3
0xab083028
· blocks 1
#4
0xab083028
#5
0x6ad2e98b
#6
execOrders
#7
updatePriceFeedsIfNecessary
#8
0x3f5c179b
#10
execFwdPositionOpsV2
#11
updateDataFeedsValuesPartial
#9
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1af7d55b…9c5e
0xa6afd3…d132
4 touches
1 conflict
0x222fc893…acc9
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1c9af259…b96c
0xa6afd3…d132
3 touches
1 conflict
0x498bf0b7…f1aa
0xa6afd3…d132
3 touches
1 conflict
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
0x2b46c0…1669
2 touches
0 conflicts
0x40970e69…da50
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
0x1af7d55bb1…469c5e
Audit this contract →
← previous block
·
next block →
recent activity