pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,990,501
← previous block
next block →
recent activity
Analyzing
Block #85,990,501
37 transactions · 25 stateful · 2026-07-06 14:01:06 UTC
Parallelism
86
/100
Blocked
44
%
Avg conflicts / tx
0.46
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,990,501
· 37 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x67098489
· blocks 3
#3
0xb264ae19
#4
0x6a4bb59a
· blocks 1
#6
0x0c7abd22
· blocks 1
#8
execute
· blocks 1
#10
0x0fbe0059
#13
updatePrices
#14
updatePrices
#15
execOrders
· blocks 2
#16
0x6a4bb599
#18
0x0c7abd22
#19
0x0c7abd22
#20
0x6a4bb599
#21
0x62be7533
#22
execFwdPositionOps
#23
execFwdPositionOps
· blocks 1
#26
0x4f819052
#27
createModule
#28
0xed82b078
#29
0xed82b078
#30
updateDataFeedsValuesPartial
#31
updateDataFeedsValuesPartial
#32
setData
#35
redeemDelegations
#36
0xc7e3ec2c
#2
0x50a0b275
· blocks 2
#7
0x6a4bb59a
#17
0x0c7abd22
#33
execOrders
· blocks 1
#5
0xaf5e395a
· blocks 3
#34
execOrders
#9
0xe3a3c9cc
#11
0xab083028
· blocks 2
#24
rebalanceFor
#12
0xab083028
#25
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w2
6
w0
7
w1
8
w0
9
w3
11
w3
12
w4
15
w0
17
w1
23
w0
24
w3
25
w4
33
w1
34
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9fc8b97d…96da
0x2a68ba…90c5
4 touches
1 conflict
0x178db37f…debb
0x34b655…2a6f
4 touches
1 conflict
0x75eb421e…ccae
0x34b655…2a6f
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