pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,497,453
← previous block
next block →
recent activity
Analyzing
Block #97,497,453
34 transactions · 28 stateful · 2026-08-20 01:42:21 UTC
Parallelism
68
/100
Blocked
64
%
Avg conflicts / tx
1.09
Longest chain
11
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,497,453
· 34 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
#6
setData
#7
0xab083028
#8
0xa96df62f
#12
execOrder
· blocks 1
#15
execOrder
· blocks 1
#16
execPerpOps
#17
updatePrices
#18
updatePrices
#19
updatePrices
#20
updatePrices
#23
updateDataFeedsValuesPartial
#24
updateDataFeedsValuesPartial
#32
0x59558d29
#33
execOrders
#2
0x0c7abd22
· blocks 5
#27
execFwdPositionOpsV2
#3
0x0c7abd22
· blocks 4
#26
batchUpdate
· blocks 2
#4
0x0c7abd22
· blocks 1
#25
0x3f5c179b
· blocks 1
#29
0xed82b078
· blocks 2
#5
0x0c7abd22
· blocks 5
#30
0xed82b078
· blocks 1
#9
execOrders
· blocks 5
#28
execFwdPositionOpsV2
#31
0xed82b078
#10
execOrders
#11
execOrder
· blocks 1
#13
execOrder
· blocks 2
#14
execOrder
· blocks 1
#21
execOrders
· blocks 1
#22
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
9
w5
10
w6
11
w6
13
w7
14
w8
21
w9
25
w3
26
w2
28
w5
30
w4
31
w5
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x886f7fe6…8b7a
0x34b655…2a6f
10 touches
10 conflicts
0xbb270d8e…b22e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x69017fce…85bb
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot
0x886f7fe654…c88b7a
Audit this contract →
← previous block
·
next block →
recent activity