pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,264,808
← previous block
next block →
recent activity
Analyzing
Block #98,264,808
38 transactions · 30 stateful · 2026-08-22 18:31:15 UTC
Parallelism
87
/100
Blocked
43
%
Avg conflicts / tx
0.66
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,264,808
· 38 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
#2
0x0c7abd22
· blocks 5
#3
execute_route
#4
0x575c0012
#5
0xdf921160
· blocks 4
#6
0x7b84f330
#7
0x7b84f330
· blocks 1
#8
exactOutputSingle
#10
0x41a8f47c
#11
0x41a8f47c
#13
execOrders
#16
execOrders
#19
execOrder
· blocks 3
#20
0x4cb2db39
#21
0x59558d29
#22
execPerpOps
#23
execPerpOps
#27
execFwdPositionOpsV2
#28
setData
#29
updatePriceFeedsIfNecessary
#30
execFwdPositionOpsV2
· blocks 1
#32
execFwdPositionOpsV2
#34
execOrders
· blocks 1
#36
0x7b84f330
#9
0x41a8f47c
· blocks 4
#17
0x0c7abd22
· blocks 1
#24
execOrders
· blocks 2
#33
0xed82b078
#35
execOrders
#37
0x7b84f330
#12
updatePrices
#14
0xab083028
· blocks 1
#18
0x0c7abd22
#25
execFwdPositionOpsV2
· blocks 1
#15
0xab083028
· blocks 1
#26
execFwdPositionOpsV2
#31
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
7
w0
9
w1
12
w2
14
w2
15
w3
17
w1
18
w2
19
w0
24
w1
25
w2
26
w3
30
w0
31
w4
33
w1
34
w0
35
w1
37
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xa2869417…b1cb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6b285e26…38e4
0xd32edf…ff58
5 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
0xf3d7a307cc…f14d63
Audit this contract →
← previous block
·
next block →
recent activity