pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,772,891
← previous block
next block →
recent activity
Analyzing
Block #98,772,891
36 transactions · 30 stateful · 2026-08-24 13:43:50 UTC
Parallelism
81
/100
Blocked
50
%
Avg conflicts / tx
0.81
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,772,891
· 36 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
· blocks 1
#1
0x0c7abd22
· blocks 2
#3
execute_route
#4
exactInputSingle
#5
0x928e4afa
· blocks 2
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
updatePrices
#11
0x32d01e04
#12
0x6a8c4b0e
#13
updateDataFeedsValuesPartial
#16
0x6a8c4b0d
#17
execOrders
· blocks 2
#19
0x59558d29
#20
execPerpOps
#23
handleOps
#28
forward
#30
setData
#31
execOrders
#33
execOrders
#2
0x0c7abd22
· blocks 5
#14
delegate
#15
0x5acec890
· blocks 1
#21
execFwdPositionOpsV2
· blocks 3
#10
0xab083028
#18
execOrders
· blocks 1
#22
execFwdPositionOpsV2
· blocks 2
#24
0x3f5c179b
· blocks 3
#25
batchUpdate
· blocks 2
#27
execFwdPositionOpsV2
· blocks 1
#26
0xed82b078
· blocks 1
#32
execOrders
· blocks 2
#29
0xed82b078
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
1
w0
2
w1
5
w0
10
w2
14
w1
15
w1
17
w0
18
w2
21
w1
22
w2
24
w2
25
w3
26
w4
27
w3
29
w5
32
w4
34
w5
35
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x065ff70b…356d
0x40c49f…2af0
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3f81bcfb…2905
0x40c49f…2af0
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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:
0x40c49f17…d22af0
10 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity