pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,898,325
← previous block
next block →
recent activity
Analyzing
Block #97,898,325
40 transactions · 29 stateful · 2026-08-21 11:41:05 UTC
Parallelism
88
/100
Blocked
31
%
Avg conflicts / tx
0.4
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,898,325
· 40 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0xa9b28aa6
#2
executePacked
· blocks 2
#3
batchCancelOrders
#4
exactInputSingle
#5
0x41a8f47c
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
updatePrices
#11
updatePrices
#12
execOrders
· blocks 1
#14
0xab083028
· blocks 2
#15
0xab083028
#16
0x32d01e04
· blocks 1
#17
0xab083028
#18
execOrders
#19
execOrders
· blocks 1
#21
0xb2d4797b
#22
execOrder
#23
execOrder
· blocks 1
#24
0xbb1740dd
#25
execPerpOps
#26
0xe3a3c9cc
#28
execFwdPositionOpsV2
#29
execFwdPositionOpsV2
#30
0x3f5c179b
#37
setData
#38
0xc3c4bf…3ae9
#39
0x59558d29
#13
execOrders
· blocks 3
#20
execOrders
#31
0x3f5c179b
· blocks 1
#27
execFwdPositionOpsV2
· blocks 2
#33
execOrders
#35
0xed82b078
· blocks 1
#32
execFwdPositionOpsV2
· blocks 1
#36
0xed82b078
#34
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
12
w0
13
w1
14
w0
16
w0
19
w0
20
w1
23
w0
27
w2
31
w1
32
w3
33
w2
34
w4
35
w2
36
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xebb541cb…a721
0xa6afd3…d132
6 touches
3 conflicts
0x0d8152a0…f7f4
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x309f47c0…e1cf
0x34b655…2a6f
4 touches
1 conflict
0x3b2dfb32…949b
0x34b655…2a6f
4 touches
1 conflict
0x4324ffc0…19cb
0x34b655…2a6f
4 touches
1 conflict
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: MarginAccount
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity