pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,080,968
← previous block
next block →
recent activity
Analyzing
Block #98,080,968
35 transactions · 31 stateful · 2026-08-22 03:05:38 UTC
Parallelism
77
/100
Blocked
58
%
Avg conflicts / tx
0.97
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,080,968
· 35 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
0x7b84f330
· blocks 1
#2
0xaf5e395a
· blocks 3
#3
0x6ad2e98b
#6
execOrders
· blocks 3
#8
0xefb04d…bd75
#9
0xb2d4797b
#10
0x59558d29
#11
execPerpOps
· blocks 1
#12
execPerpOps
#14
execPerpOps
#15
0x5acec890
· blocks 4
#21
execFwdPositionOpsV2
· blocks 2
#22
0x62be7533
#26
0xed82b078
· blocks 1
#29
exactInputSingle
#30
setData
#4
0xab083028
· blocks 3
#7
execOrders
#13
execPerpOps
#16
0x928e4afa
· blocks 4
#27
0xed82b078
#34
0x7b84f330
#5
0x8263f5d9
· blocks 2
#17
0x5acec890
· blocks 1
#24
0x3f5c179b
#18
0x5acec890
· blocks 1
#19
0xf78cb219
#25
0x3f5c179b
#20
execFwdPositionOpsV2
· blocks 3
#23
execFwdPositionOpsV2
· blocks 2
#31
execOrders
· blocks 2
#28
execFwdPositionOpsV2
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
5
w2
6
w0
7
w1
11
w0
13
w1
15
w0
16
w1
17
w2
18
w3
19
w3
20
w4
23
w5
24
w2
25
w3
31
w5
32
w6
34
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd7443f37…eb79
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
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:
Kuru Exchange: MarginAccount
6 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity