pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,838,373
← previous block
next block →
recent activity
Analyzing
Block #86,838,373
35 transactions · 27 stateful · 2026-07-10 12:27:21 UTC
Parallelism
74
/100
Blocked
52
%
Avg conflicts / tx
1
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,838,373
· 35 txs across 9 waves · depth 9
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
exactInput
#3
0x6a50e5a1
#4
exactInputSingle
#6
updatePrices
#7
updatePrices
#8
0x6a50e5a1
#9
0x6a50e5a1
#10
0x5a5d9a99
· blocks 6
#12
updateDataFeedsValuesPartial
#15
0x3f5c179b
#16
0x3f5c179b
#21
0xed82b078
#23
setData
#24
0xec0767…b8f0
#25
0x3663f7…0793
#26
0xa535b9…f7dc
#27
0xdf1811…79fd
#33
0xc7e3ec2c
#34
0xc7e3ec2c
#5
0x0c7abd22
· blocks 2
#11
0x5a5d9a99
· blocks 2
#13
execFwdPositionOps
· blocks 4
#22
0xed82b078
#14
execFwdPositionOps
· blocks 6
#18
batchUpdate
· blocks 1
#17
execFwdPositionOps
· blocks 2
#19
0xed82b078
#20
execFwdPositionOps
#28
execOrders
· blocks 4
#29
execOrders
· blocks 3
#30
execOrders
· blocks 2
#31
execOrders
· blocks 1
#32
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
10
w0
11
w1
13
w1
14
w2
17
w3
18
w2
19
w3
20
w4
22
w1
28
w4
29
w5
30
w6
32
w8
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xf7ab945c…597e
0x34b655…2a6f
8 touches
6 conflicts
0x8cc1393f…07fb
0x34b655…2a6f
6 touches
3 conflicts
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
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:
Perpl
10 conflicts on slot
0xf2f4727df6…a5cdb7
Audit this contract →
← previous block
·
next block →
recent activity