pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,431,544
← previous block
next block →
recent activity
Analyzing
Block #91,431,544
36 transactions · 32 stateful · 2026-07-29 19:51:13 UTC
Parallelism
81
/100
Blocked
59
%
Avg conflicts / tx
0.97
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,431,544
· 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
0x0c7abd22
#2
0x0c7abd22
· blocks 1
#3
execute_route
· blocks 2
#6
0x6a6a5a29
#8
exactInputSingle
#10
execOrder
#12
execPerpOps
#13
execPerpOps
#14
updatePrices
· blocks 3
#18
0x5a5d9a99
· blocks 2
#21
updateDataFeedsValuesPartial
#22
updateDataFeedsValuesPartial
#25
handleOps
#30
setData
#31
execOrders
· blocks 2
#34
0x59558d29
· blocks 1
#4
execute_route
· blocks 2
#9
execute
#11
0xab083028
· blocks 1
#15
updatePrices
· blocks 2
#19
0x5a5d9a99
· blocks 5
#32
execOrders
· blocks 1
#35
0x59558d29
#5
exactInput
· blocks 1
#16
updatePrices
· blocks 1
#20
0x5a5d9a99
#23
execFwdPositionOps
· blocks 4
#27
0xed82b078
#7
exactInputSingle
#17
updatePrices
#24
execFwdPositionOps
· blocks 2
#26
execFwdPositionOps
· blocks 3
#28
execOrders
· blocks 2
#29
execOrders
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w2
7
w3
9
w1
11
w1
14
w0
15
w1
16
w2
17
w3
18
w0
19
w1
20
w2
23
w2
24
w3
26
w4
27
w2
28
w5
29
w6
33
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x92115abd…ad76
0x34b655…2a6f
8 touches
6 conflicts
0x83dea465…8a72
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
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:
0x48cba278…e2b48b
6 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity