pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,925,445
← previous block
next block →
recent activity
Analyzing
Block #98,925,445
38 transactions · 29 stateful · 2026-08-25 02:31:32 UTC
Parallelism
87
/100
Blocked
55
%
Avg conflicts / tx
0.76
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,925,445
· 38 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0xc7b1f3…2cac
#2
0xdef029…0a89
#3
0xdf921160
· blocks 6
#4
executePacked
#5
swap
#6
0x5acec890
· blocks 3
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
updatePrices
#14
execOrders
· blocks 1
#15
0x6a8cfefb
· blocks 1
#16
execOrders
#19
0x59558d29
#20
0xb414539a
#21
execPerpOps
#23
0x41a8f47c
#26
execFwdPositionOpsV2
· blocks 1
#27
0x3f5c179b
· blocks 1
#31
forward
#35
setData
#11
0xab083028
· blocks 5
#13
0x8263f5d9
· blocks 3
#17
0x5acec890
· blocks 1
#32
execFwdPositionOpsV2
· blocks 1
#33
0xed82b078
#34
0x6a8cfefb
#36
execOrders
· blocks 1
#12
0x6ad2e98b
· blocks 2
#18
0x5acec890
· blocks 1
#28
0x3f5c179b
· blocks 1
#29
0x0c7abd22
#37
execOrders
#22
0xe3a3c9cc
· blocks 1
#25
execFwdPositionOpsV2
#30
batchUpdate
#24
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w0
11
w1
12
w2
13
w1
14
w0
15
w0
17
w1
18
w2
22
w3
24
w4
25
w3
26
w0
28
w2
29
w2
30
w3
32
w1
34
w1
36
w1
37
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x378219ab…77a7
0x065c9d…c394
5 touches
3 conflicts
0x9d6a99f9…da64
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb484f60a…81af
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
10 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity