pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,079,413
← previous block
next block →
recent activity
Analyzing
Block #98,079,413
37 transactions · 32 stateful · 2026-08-22 02:57:49 UTC
Parallelism
78
/100
Blocked
50
%
Avg conflicts / tx
0.97
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,079,413
· 37 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
0xf78cb219
#2
0x7b84f330
· blocks 1
#3
0xaf5e395a
#4
0x41a8f47c
#5
0x41a8f47c
#6
0x41a8f47c
#7
setData
#8
execOrders
#9
0xab083028
· blocks 1
#12
execOrders
· blocks 3
#15
0x59558d29
#16
execPerpOps
#17
execPerpOps
#18
0x5acec890
· blocks 4
#22
0x62be7533
#24
executeBatch
#26
forward
#27
forward
#31
execOrders
· blocks 3
#35
modifyLiquidities
#10
0xab083028
· blocks 5
#13
execOrders
· blocks 1
#19
0x5acec890
· blocks 1
#36
0x7b84f330
#11
0x8263f5d9
#14
execOrders
· blocks 3
#25
0x0c7abd22
· blocks 3
#20
0x5acec890
· blocks 2
#28
0xed82b078
· blocks 2
#21
execFwdPositionOpsV2
· blocks 3
#29
0xed82b078
· blocks 1
#23
execFwdPositionOpsV2
#30
0xed82b078
#32
execOrders
· blocks 2
#33
execOrders
· blocks 1
#34
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w0
10
w1
11
w2
12
w0
13
w1
14
w2
18
w0
19
w1
20
w3
21
w4
23
w5
25
w2
28
w3
29
w4
30
w5
32
w5
34
w7
36
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xa02838a3…bc54
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x49299fcf…c552
0x34b655…2a6f
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
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: Market-MON/USDC
10 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity