pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,496,913
← previous block
next block →
recent activity
Analyzing
Block #98,496,913
34 transactions · 29 stateful · 2026-08-23 13:59:22 UTC
Parallelism
76
/100
Blocked
59
%
Avg conflicts / tx
1.09
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,496,913
· 34 txs across 8 waves · depth 8
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0x6a8afd32
#4
setData
#7
execOrders
· blocks 1
#10
0x59558d29
#11
execPerpOps
#12
execPerpOps
#14
0x41a8f47c
#15
0x928e4afa
· blocks 1
#16
exactInputSingle
#17
execFwdPositionOpsV2
· blocks 3
#18
execFwdPositionOpsV2
#20
verifyOracleProofV2
#21
0x5de3085d
#24
0xed82b078
· blocks 1
#28
0xb8024e79
#2
0x0c7abd22
· blocks 4
#8
execOrders
#9
0x4cb2db39
#19
execFwdPositionOpsV2
· blocks 2
#5
0xab083028
· blocks 3
#22
execFwdPositionOpsV2
· blocks 5
#6
0xab083028
· blocks 3
#23
execOrders
· blocks 1
#27
execFwdPositionOpsV2
#29
execOrders
· blocks 4
#13
0x41a8f47c
#25
0xed82b078
· blocks 1
#30
execOrders
· blocks 3
#26
0xed82b078
#31
execOrders
· blocks 2
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
6
w3
7
w0
8
w1
9
w1
13
w4
15
w0
17
w0
19
w1
22
w2
23
w3
25
w4
26
w5
27
w3
29
w3
30
w4
31
w5
33
w7
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbbee74c2…567a
0x065c9d…c394
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
10 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity