pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,836,845
← previous block
next block →
recent activity
Analyzing
Block #98,836,845
38 transactions · 26 stateful · 2026-08-24 19:05:48 UTC
Parallelism
84
/100
Blocked
50
%
Avg conflicts / tx
0.63
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,836,845
· 38 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
execute_route
· blocks 2
#2
0xdf921160
· blocks 2
#3
0x6a8c9684
#4
0x6a8c9684
#5
0x6a8c9684
#6
exactInputSingle
#7
exactInputSingle
#9
setData
#10
updatePrices
· blocks 1
#11
updatePrices
#12
updatePrices
#13
updatePrices
#14
updatePrices
#16
0xab083028
· blocks 3
#18
0xab083028
#19
execOrders
· blocks 3
#21
0x5acec890
#23
execOrder
#25
0x3f5c179b
· blocks 2
#29
execFwdPositionOpsV2
#30
execFwdPositionOpsV2
#32
0x6a8c9684
#33
0xa97804…119d
#34
0x35f7c2…6190
#8
execute
· blocks 1
#15
updatePrices
#17
0xab083028
· blocks 1
#20
execOrders
· blocks 2
#22
execOrder
· blocks 1
#27
0xed82b078
#28
0xed82b078
#31
batchUpdate
#24
0x62be7533
#26
execFwdPositionOpsV2
· blocks 3
#35
execOrders
· blocks 2
#36
execOrders
· blocks 1
#37
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
8
w1
10
w0
15
w1
16
w0
17
w1
19
w0
20
w1
22
w1
24
w2
25
w0
26
w2
27
w1
28
w1
31
w1
35
w3
36
w4
37
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
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:
Uniswap: PoolManager
3 conflicts on slot
0x01e7b86585…4d6e6d
Audit this contract →
← previous block
·
next block →
recent activity