pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,486,031
← previous block
next block →
recent activity
Analyzing
Block #99,486,031
35 transactions · 29 stateful · 2026-08-27 01:39:25 UTC
Parallelism
74
/100
Blocked
66
%
Avg conflicts / tx
1.49
Longest chain
9
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,486,031
· 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 8
#6
0x6a8f95c5
· blocks 1
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
setData
#11
execOrders
#14
updateDataFeedsValuesPartial
#15
0x6a8f95c5
#19
0x59558d29
#21
0x6cfade05
#24
0x3f5c179b
#28
redeemDelegations
#29
redeemDelegations
#30
execFwdPositionOpsV2
· blocks 4
#2
0x0c7abd22
· blocks 7
#20
0x6a8f95c5
#3
0x0c7abd22
· blocks 10
#25
0x3f5c179b
#4
0x0c7abd22
· blocks 5
#13
0x928e4afa
#16
execOrder
· blocks 1
#17
execOrder
· blocks 2
#5
0x0c7abd22
· blocks 3
#18
execOrder
· blocks 1
#23
execFwdPositionOpsV2
· blocks 1
#27
0xed82b078
#12
0x0c7abd22
· blocks 2
#31
execFwdPositionOpsV2
· blocks 3
#22
0x0c7abd22
· blocks 1
#32
execOrders
· blocks 2
#26
0x0c7abd22
#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
w1
3
w2
4
w3
5
w4
12
w5
13
w3
16
w3
17
w3
22
w6
23
w4
25
w2
26
w7
27
w4
31
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa9afb5d…4a9f
0xd32edf…ff58
15 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0xada193dc…5c79
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot
0xfa9afb5dc7…dc4a9f
Audit this contract →
← previous block
·
next block →
recent activity