pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,197,380
← previous block
next block →
recent activity
Analyzing
Block #97,197,380
13 transactions · 11 stateful · 2026-08-19 00:00:40 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,197,380
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xa96df62f
#3
matchOrders
· blocks 1
#5
0xab083028
· blocks 1
#7
updatePrices
#8
updateDataFeedsValuesPartial
#9
batchUpdate
#10
forward
#11
setData
#12
execOrders
#4
matchOrders
#6
0x32d01e04
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4c946a4…b8d4
0x754704…b603
4 touches
1 conflict
0x45436af6…437f
0x99c7a7…8bf0
4 touches
1 conflict
0x66300207…c47a
0x99c7a7…8bf0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0x15c6ded9…48e7
0x754704…b603
4 touches
1 conflict
0x5a7e4e98…1f3b
0x754704…b603
4 touches
1 conflict
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
0xd4c946a466…37b8d4
Audit this contract →
← previous block
·
next block →
recent activity