pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,838,427
← previous block
next block →
recent activity
Analyzing
Block #98,838,427
36 transactions · 33 stateful · 2026-08-24 19:13:46 UTC
Parallelism
81
/100
Blocked
36
%
Avg conflicts / tx
0.81
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,838,427
· 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
0x67098489
#2
0xdf921160
#3
0xa96df62f
#4
0x5acec890
· blocks 2
#5
setData
#6
0xab083028
· blocks 4
#9
updateDataFeedsValuesPartial
#10
execOrders
#12
execOrders
· blocks 2
#13
execOrder
· blocks 1
#14
0x59558d29
#15
execOrders
· blocks 2
#16
execPerpOps
· blocks 1
#19
execFwdPositionOpsV2
· blocks 1
#22
0xed82b078
· blocks 1
#25
0x6a8c9862
#27
execOrders
· blocks 1
#28
execOrders
#29
execOrders
#30
execOrders
#31
execOrders
#33
execOrders
· blocks 1
#35
execOrders
#7
0xab083028
· blocks 3
#11
0x928e4afa
· blocks 2
#17
execPerpOps
#23
0xed82b078
· blocks 1
#8
0x8263f5d9
#18
execFwdPositionOpsV2
· blocks 2
#21
0x0c7abd22
· blocks 1
#20
execFwdPositionOpsV2
· blocks 1
#24
0xed82b078
#26
execOrders
· blocks 2
#32
execOrders
· blocks 1
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
8
w2
11
w1
12
w0
13
w0
15
w0
16
w0
17
w1
18
w2
19
w0
20
w3
21
w2
22
w0
23
w1
24
w3
26
w4
32
w5
34
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x2a354a63…0515
0x065c9d…c394
6 touches
3 conflicts
0x8e66da19…66b6
0x065c9d…c394
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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:
Kuru Exchange: Market-MON/USDC
6 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity