pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,139,764
← previous block
next block →
recent activity
Analyzing
Block #85,139,764
23 transactions · 22 stateful · 2026-07-02 15:33:21 UTC
Parallelism
87
/100
Blocked
23
%
Avg conflicts / tx
0.35
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,139,764
· 23 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
execute
· blocks 2
#4
exactOutputSingle
#5
exactOutputSingle
#6
execute
#7
exactOutputSingle
#8
removeLiquidityNATIVE
#9
updatePrices
#11
execPerpOps
· blocks 1
#13
updateDataFeedsValuesPartial
#14
updateDataFeedsValuesPartial
#16
0x3f5c179b
#17
forward
#18
createModule
#19
setData
#20
execOrders
· blocks 1
#22
0xc7e3ec2c
#2
0x0c7abd22
· blocks 1
#10
0x6f0a5635
· blocks 1
#12
execPerpOps
#21
execOrders
#15
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
10
w1
11
w0
12
w1
15
w2
20
w0
21
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x2065a592…7152
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xc6a8c250…737a
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:
Uniswap: PoolManager
3 conflicts on slot
0x01e7b86585…4d6e6d
Audit this contract →
← previous block
·
next block →
recent activity