pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,851,668
← previous block
next block →
recent activity
Analyzing
Block #99,851,668
39 transactions · 29 stateful · 2026-08-28 08:32:51 UTC
Parallelism
90
/100
Blocked
45
%
Avg conflicts / tx
0.62
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,851,668
· 39 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
· blocks 6
#3
execute
· blocks 3
#4
multicall
#7
matchOrders
#8
setData
#9
execute
#10
updatePrices
· blocks 1
#12
0x5acec890
· blocks 1
#13
updatePrices
#14
updatePrices
#16
0x32d01e04
#17
0x8263f5d9
#18
0xab083028
#19
updateDataFeedsValuesPartial
#20
0x5acec890
#21
0x5acec890
#22
0x5acec890
#24
0x0c7abd22
· blocks 1
#26
execPerpOps
#27
execPerpOps
#28
0xe3a3c9cc
#29
execOrders
#33
execFwdPositionOpsV2
#36
0x6a91482b
· blocks 1
#38
exactInputSingle
#2
0xab083028
· blocks 2
#5
main_all
· blocks 2
#11
updatePrices
#15
0xbe5a93b8
· blocks 2
#23
0x928e4afa
· blocks 1
#37
0x6a91482b
#6
main_all
· blocks 1
#25
execute
· blocks 1
#31
0x0c7abd22
· blocks 1
#32
execFwdPositionOpsV2
· blocks 1
#30
0x62be7533
#34
0xed82b078
#35
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
5
w1
6
w2
10
w0
11
w1
12
w0
15
w1
23
w1
24
w0
25
w2
30
w3
31
w2
32
w2
34
w3
35
w3
36
w0
37
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
8 touches
6 conflicts
0x8ef2c6bd…b374
0x065c9d…c394
7 touches
6 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
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:
Uniswap: PoolManager
6 conflicts on slot
0x01e7b86585…4d6e6d
Audit this contract →
← previous block
·
next block →
recent activity