pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,565,304
← previous block
next block →
recent activity
Analyzing
Block #86,565,304
35 transactions · 28 stateful · 2026-07-09 06:00:44 UTC
Parallelism
71
/100
Blocked
64
%
Avg conflicts / tx
1.31
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,565,304
· 35 txs across 10 waves · depth 10
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x6a4f3984
#4
0x6a4f3984
#5
0x6a4f3984
#9
updatePrices
#10
execOrders
#11
0x6a4f3984
#12
0x5a5d9a99
· blocks 5
#16
0x6a4f3984
#19
updateDataFeedsValuesPartial
#21
0x3f5c179b
#25
transfer
#26
setData
#27
0x300b1a…cb59
#33
0x5d2fd812
#34
0xc7e3ec2c
#2
0x0c7abd22
· blocks 1
#13
0x5a5d9a99
· blocks 5
#22
execFwdPositionOps
· blocks 3
#6
0x0c7abd22
· blocks 5
#14
0x5a5d9a99
· blocks 4
#7
0xab083028
· blocks 4
#15
0x5a5d9a99
· blocks 1
#18
execFwdPositionOps
· blocks 2
#8
0x6ad2e98b
#17
execFwdPositionOps
· blocks 1
#20
0x3f5c179b
· blocks 2
#23
0xed82b078
· blocks 1
#28
execOrders
· blocks 4
#24
0xed82b078
#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
2
w1
6
w2
7
w3
8
w4
12
w0
13
w1
14
w2
15
w3
18
w3
20
w4
22
w1
23
w5
24
w6
29
w6
32
w9
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
8 touches
6 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x70ff9262…8d80
0x34b655…2a6f
6 touches
3 conflicts
0xd4230a60…bd13
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:
Kuru Exchange: Market-WETH/USDC
10 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity