pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,840,740
← previous block
next block →
recent activity
Analyzing
Block #98,840,740
35 transactions · 28 stateful · 2026-08-24 19:25:24 UTC
Parallelism
71
/100
Blocked
57
%
Avg conflicts / tx
1.46
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,840,740
· 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
0xa96df62f
#2
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#6
updatePrices
#7
updatePrices
#8
0x6a8c9b1c
#9
execOrders
#10
0x6a8c9b1c
#11
0x5acec890
· blocks 2
#12
0x6a8c9b1c
#14
execOrders
#16
0x59558d29
#18
execFwdPositionOpsV2
#20
0xed82b078
· blocks 2
#25
0x6a8c9b1c
#26
setData
#27
execOrders
· blocks 7
#3
updatePrices
#13
0x5acec890
· blocks 6
#21
0xed82b078
· blocks 3
#28
execOrders
· blocks 6
#15
execOrder
· blocks 1
#22
0xed82b078
· blocks 2
#17
execFwdPositionOpsV2
· blocks 5
#23
0xed82b078
· blocks 1
#19
redeemDelegations
#24
0xed82b078
#29
execOrders
· blocks 5
#30
execOrders
· blocks 4
#31
execOrders
· blocks 3
#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
2
w0
3
w1
11
w0
13
w1
15
w2
17
w3
19
w4
20
w0
21
w1
22
w2
23
w3
24
w4
27
w0
28
w1
29
w4
30
w5
33
w8
34
w9
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x886db264…846e
0x34b655…2a6f
6 touches
3 conflicts
0x8b7fe709…9d99
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
28 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity