pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,755,376
← previous block
next block →
recent activity
Analyzing
Block #98,755,376
35 transactions · 34 stateful · 2026-08-24 12:15:41 UTC
Parallelism
69
/100
Blocked
47
%
Avg conflicts / tx
1.46
Longest chain
11
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,755,376
· 35 txs across 11 waves · depth 11
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
wave
w10
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#4
updatePrices
#5
0xab083028
· blocks 2
#7
execOrders
#8
0x6a8c3664
#9
0x59558d29
#10
execPerpOps
#11
execPerpOps
#13
execFwdPositionOpsV2
#16
forward
#17
0xed82b078
#19
setData
#21
execOrders
· blocks 1
#23
execOrders
#26
execOrders
#28
execOrders
· blocks 1
#30
execOrders
#32
execOrders
#2
0x0c7abd22
· blocks 5
#6
0xab083028
· blocks 1
#14
0x3f5c179b
#3
0x0c7abd22
· blocks 3
#12
execFwdPositionOpsV2
· blocks 3
#18
0xed82b078
#15
execFwdPositionOpsV2
· blocks 3
#20
execOrders
· blocks 7
#22
execOrders
· blocks 6
#34
execOrders
#24
execOrders
· blocks 5
#25
execOrders
· blocks 4
#27
execOrders
· blocks 3
#29
execOrders
· blocks 2
#31
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
w1
3
w2
5
w0
6
w1
12
w2
14
w1
15
w3
18
w2
20
w3
22
w4
24
w5
25
w6
27
w7
29
w8
31
w9
33
w10
34
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x45b67460…28a7
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x737acb78…fce8
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:
Perpl
28 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity