pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,067,660
← previous block
next block →
recent activity
Analyzing
Block #98,067,660
37 transactions · 33 stateful · 2026-08-22 01:58:39 UTC
Parallelism
78
/100
Blocked
58
%
Avg conflicts / tx
0.92
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,067,660
· 37 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 6
#4
execute_route
#5
0x7b84f330
· blocks 1
#6
exactInputSingle
#7
0xa96df62f
#8
setData
#12
0x6ad2e98b
#13
0xab083028
#14
execOrders
· blocks 3
#17
0x59558d29
#18
execPerpOps
#19
0x6b8f732b
#20
0x6b8f732b
#21
updatePrices
· blocks 1
#25
0x5acec890
· blocks 1
#27
0x6b8f732b
#32
transfer
#2
0x0c7abd22
· blocks 5
#10
0xab083028
· blocks 1
#15
execOrders
· blocks 2
#22
updatePrices
#36
0x7b84f330
#3
0x0c7abd22
· blocks 2
#9
execOrders
#11
0xab083028
#16
execOrders
· blocks 1
#23
0x5acec890
· blocks 2
#24
execOrder
· blocks 2
#26
0x5acec890
· blocks 2
#30
0xed82b078
#31
0xed82b078
#28
execFwdPositionOpsV2
· blocks 2
#29
execFwdPositionOpsV2
#33
execOrders
· blocks 2
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w0
9
w2
10
w1
11
w2
14
w0
15
w1
16
w2
21
w0
22
w1
23
w2
24
w3
26
w3
28
w4
30
w3
31
w3
33
w5
36
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity