pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,575,734
← previous block
next block →
recent activity
Analyzing
Block #98,575,734
35 transactions · 31 stateful · 2026-08-23 20:50:26 UTC
Parallelism
89
/100
Blocked
45
%
Avg conflicts / tx
0.54
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,575,734
· 35 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0xab083028
· blocks 2
#5
0x6ad2e98b
#8
execOrders
· blocks 2
#10
updateDataFeedsValuesPartial
#11
exactInputSingle
#12
0xa0ce48…e2e0
#13
0x6a8b5d89
· blocks 1
#14
0x59558d29
· blocks 1
#16
execPerpOps
#17
execPerpOps
#18
0x5acec890
#19
setData
#20
execFwdPositionOpsV2
· blocks 4
#21
execFwdPositionOpsV2
#22
updatePriceFeedsIfNecessary
#31
0x0a88e2…9634
#32
0x451912…a6e0
#33
execOrders
· blocks 1
#4
0xab083028
· blocks 2
#9
execOrders
· blocks 2
#15
0x59558d29
#24
execFwdPositionOpsV2
· blocks 1
#25
execOrders
· blocks 1
#28
execFwdPositionOpsV2
#30
0x6a8b5d8a
#6
0xab083028
· blocks 1
#23
0x3f5c179b
#26
execFwdPositionOpsV2
#27
execFwdPositionOpsV2
· blocks 1
#29
execFwdPositionOpsV2
#7
0xab083028
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w2
7
w3
8
w0
9
w1
13
w0
14
w0
15
w1
20
w0
23
w2
24
w1
25
w1
26
w2
27
w2
28
w1
29
w2
30
w1
33
w0
34
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xaef85d8c…963b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x68531239…e9a3
0x34b655…2a6f
6 touches
3 conflicts
0x640c4fb2…044a
0x34b655…2a6f
4 touches
1 conflict
0x9ad82ccb…b08b
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xbd9491f7…dd92
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity