pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,850,832
← previous block
next block →
recent activity
Analyzing
Block #98,850,832
37 transactions · 35 stateful · 2026-08-24 20:16:10 UTC
Parallelism
84
/100
Blocked
40
%
Avg conflicts / tx
0.65
Longest chain
6
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,850,832
· 37 txs across 6 waves · depth 6
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
#0
syscallReward
#1
execute
#2
0x8263f5d9
#3
0x0c7abd22
#4
0x5acec890
· blocks 2
#6
execOrders
· blocks 3
#8
0x59558d29
#9
execPerpOps
· blocks 1
#11
execPerpOps
#12
execPerpOps
#14
0x62be7533
#15
execFwdPositionOpsV2
#16
handleOps
#18
0xed82b078
· blocks 4
#20
0xed82b078
#21
0xed82b078
· blocks 1
#28
0x6a8ca702
#29
setData
#31
execOrders
#32
execOrders
#33
execOrders
#35
execOrders
#36
execOrders
#5
0x5acec890
· blocks 1
#7
execOrders
· blocks 1
#10
execPerpOps
#19
0xed82b078
· blocks 3
#27
0xed82b078
#30
execOrders
#13
execFwdPositionOpsV2
· blocks 2
#22
0xed82b078
· blocks 3
#17
execFwdPositionOpsV2
#23
0xed82b078
· blocks 2
#26
0xed82b078
#34
execOrders
#24
0xed82b078
· blocks 1
#25
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w0
7
w1
9
w0
10
w1
13
w2
17
w3
18
w0
19
w1
21
w0
22
w2
23
w3
24
w4
25
w5
26
w3
27
w1
30
w1
34
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x39773cec…38ed
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x952dd1d7…897a
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
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity