pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,559,869
← previous block
next block →
recent activity
Analyzing
Block #98,559,869
37 transactions · 34 stateful · 2026-08-23 19:27:30 UTC
Parallelism
84
/100
Blocked
38
%
Avg conflicts / tx
0.73
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,559,869
· 37 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
0xa96df62f
#2
0xa96df62f
#3
0xa96df62f
#4
0xa96df62f
#5
updatePrices
#6
0x6ad2e98b
#7
0xab083028
· blocks 1
#9
0xab083028
· blocks 2
#11
execOrders
#12
exactInputSingle
#13
0xf5b96e…20ce
#14
0x30efd3…0cc4
#15
0x59558d29
· blocks 1
#17
updateDataFeedsValuesPartial
#18
execPerpOps
#19
execPerpOps
#20
execFwdPositionOpsV2
· blocks 7
#23
placeBet
#26
bet
#30
execFwdPositionOpsV2
#32
transfer
#33
0x6a8b4a18
· blocks 1
#35
setData
#8
0xab083028
· blocks 1
#10
0xab083028
· blocks 1
#16
0x59558d29
#21
execFwdPositionOpsV2
· blocks 6
#34
0x6a8b4a19
#22
0x3f5c179b
#24
execFwdPositionOpsV2
· blocks 1
#25
execFwdPositionOpsV2
· blocks 3
#27
0xed82b078
#28
execFwdPositionOpsV2
· blocks 2
#36
execOrders
#29
execFwdPositionOpsV2
· blocks 1
#31
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
9
w0
10
w1
15
w0
16
w1
20
w0
21
w1
22
w2
24
w2
25
w2
27
w2
28
w3
29
w4
31
w5
36
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c77b5f4…601e
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x60a536a6…ef7a
0x34b655…2a6f
8 touches
6 conflicts
0xf06fce24…887d
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x622df421…3ad6
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot
0x2c77b5f4a5…b4601e
Audit this contract →
← previous block
·
next block →
recent activity