pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,469,423
← previous block
next block →
recent activity
Analyzing
Block #102,469,423
39 transactions · 31 stateful · 2026-09-06 12:30:40 UTC
Parallelism
85
/100
Blocked
42
%
Avg conflicts / tx
0.64
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,469,423
· 39 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0x67098489
· blocks 1
#2
0x1ada0a83
· blocks 5
#3
execute
#5
0x575c0012
#6
exactInput
#7
0x4ccf0801
#9
0x6a9d5cf3
#11
0xab083028
#14
exactOutputSingle
#15
0x5acec890
· blocks 1
#16
updatePrices
· blocks 1
#18
updatePrices
#19
0x4297b034
#21
0x5acec890
#22
0x5acec890
#23
0x5acec890
#24
updateDataFeedsValuesPartial
#25
0x4cb2db39
#26
0x59558d29
#29
execFwdPositionOpsV2
· blocks 1
#30
execFwdPositionOpsV2
· blocks 1
#31
setData
#33
postStateList
#34
0x6a9d5cf3
#38
execOrders
#4
execute_route
· blocks 1
#8
executePacked
· blocks 3
#13
execute
#17
updatePrices
#32
execFwdPositionOpsV2
#35
execOrders
· blocks 2
#10
0xab083028
· blocks 4
#36
execOrders
· blocks 1
#12
0xab083028
· blocks 2
#37
execOrders
#20
0xab083028
· blocks 2
#27
0xe3a3c9cc
#28
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
8
w1
10
w2
12
w3
13
w1
15
w0
16
w0
17
w1
20
w4
27
w5
28
w5
29
w0
30
w0
32
w1
35
w1
36
w2
37
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb87af72a…aef6
0x2a68ba…90c5
10 touches
10 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x46cb45de…a566
0x188d58…ea8e
6 touches
3 conflicts
0x46cb45de…a568
0x188d58…ea8e
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 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: MarginAccount
10 conflicts on slot
0xb87af72ae5…0baef6
Audit this contract →
← previous block
·
next block →
recent activity