pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,983,000
← previous block
next block →
recent activity
Analyzing
Block #86,983,000
36 transactions · 30 stateful · 2026-07-11 04:34:00 UTC
Parallelism
81
/100
Blocked
50
%
Avg conflicts / tx
1
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,983,000
· 36 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
0x0c7abd22
· blocks 5
#2
0xbbb036a8
· blocks 2
#3
0x575c0012
#5
0x6a51c830
#7
exactOutputSingle
#8
execute
#10
0x6ad2e98b
#12
0xab083028
#13
updatePrices
#17
execPerpOps
#18
execPerpOps
#19
0x6b8f732b
#20
0x6b8f732b
#21
0x5a5d9a99
· blocks 4
#23
updateDataFeedsValuesPartial
#24
execFwdPositionOps
· blocks 3
#27
0x57368ddf
#29
execOrders
#30
setData
#35
0xc7e3ec2c
#4
exactInput
· blocks 1
#9
execute
#11
0x0c7abd22
· blocks 3
#22
0x5a5d9a99
· blocks 3
#25
execFwdPositionOps
· blocks 4
#6
exactOutputSingle
#14
0x0c7abd22
· blocks 2
#26
execFwdPositionOps
· blocks 1
#31
execOrders
· blocks 3
#15
0x0c7abd22
· blocks 1
#28
execFwdPositionOps
· blocks 1
#16
0x0c7abd22
#32
execOrders
· blocks 2
#33
execOrders
· blocks 1
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
6
w2
9
w1
11
w1
14
w2
15
w3
16
w4
21
w0
22
w1
24
w0
25
w1
26
w2
28
w3
31
w2
33
w5
34
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0ab6e31…6e6a
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xb6ed530c…d450
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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:
FastLane: FastLaneAuctionHandler
10 conflicts on slot
0xb0ab6e31a5…ff6e6a
Audit this contract →
← previous block
·
next block →
recent activity