pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,390,316
← previous block
next block →
recent activity
Analyzing
Block #98,390,316
36 transactions · 30 stateful · 2026-08-23 05:02:43 UTC
Parallelism
78
/100
Blocked
60
%
Avg conflicts / tx
1.17
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,390,316
· 36 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 3
#4
0x6a8a7f6b
· blocks 1
#5
0x6a8a7f6b
#6
0x6a8a7f6b
#8
exactInputSingle
#9
0x41a8f47c
#10
updatePrices
· blocks 6
#17
execOrders
#18
0xab083028
#19
0xab083028
#20
execOrders
#21
execOrder
· blocks 1
#22
0x59558d29
#23
0x6a8a7f6b
#27
execFwdPositionOpsV2
· blocks 1
#30
0xed82b078
#32
setData
#2
0x0c7abd22
· blocks 3
#7
0x6a8a7f6b
#11
updatePrices
· blocks 5
#28
execFwdPositionOpsV2
#3
0x0c7abd22
· blocks 3
#12
updatePrices
· blocks 4
#29
0x3f5c179b
#13
updatePrices
· blocks 3
#24
0x5acec890
· blocks 3
#26
0x0c7abd22
#14
updatePrices
· blocks 2
#25
0x5acec890
· blocks 2
#31
execFwdPositionOpsV2
· blocks 1
#15
updatePrices
· blocks 1
#33
execOrders
· blocks 2
#16
updatePrices
#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
4
w0
7
w1
10
w0
11
w1
12
w2
13
w3
14
w4
15
w5
16
w6
24
w3
25
w4
26
w3
29
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xbb3f3c…e046
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x6fd9ae7c…e97f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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:
0xbb3f3cb7…74e046
21 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity