pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,707,265
← previous block
next block →
recent activity
Analyzing
Block #96,707,265
14 transactions · 12 stateful · 2026-08-17 06:42:21 UTC
Parallelism
86
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,707,265
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
exactInput
· blocks 1
#4
exactInputSingle
#5
setData
#6
updatePrices
· blocks 1
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
0x61d59c2d
#13
execOrders
#3
exactInputSingle
#7
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0xdc370e66…83a7
0x065c9d…c394
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:
0x103de0b5…25bb55
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity