pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,735,221
← previous block
next block →
recent activity
Analyzing
Block #98,735,221
33 transactions · 28 stateful · 2026-08-24 10:34:11 UTC
Parallelism
70
/100
Blocked
61
%
Avg conflicts / tx
1.21
Longest chain
10
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,735,221
· 33 txs across 10 waves · depth 10
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
wave
w7
wave
w8
wave
w9
#0
syscallReward
#1
0x6a8c1e9b
#2
0x6a8c1e9b
#3
matchOrders
#4
0xab083028
#5
execOrders
· blocks 1
#6
0x5acec890
· blocks 4
#8
0x6a8c1e9b
#13
0x59558d29
#14
updatePrices
· blocks 3
#20
updateDataFeedsValuesPartial
#21
0x3f5c179b
· blocks 1
#24
0x6a8c1e9b
#25
setData
#31
execOrders
#32
execOrders
#7
0x5acec890
· blocks 3
#15
updatePrices
· blocks 2
#22
batchUpdate
#9
0x928e4afa
· blocks 2
#16
updatePrices
· blocks 1
#18
execFwdPositionOpsV2
· blocks 4
#10
0x5acec890
· blocks 2
#17
updatePrices
#19
execFwdPositionOpsV2
· blocks 3
#11
execOrders
· blocks 2
#23
execFwdPositionOpsV2
· blocks 2
#12
execOrders
#26
execOrders
· blocks 4
#27
execOrders
· blocks 3
#28
execOrders
· blocks 2
#29
execOrders
· blocks 1
#30
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
9
w2
10
w3
11
w4
12
w5
14
w0
15
w1
16
w2
17
w3
18
w2
19
w3
23
w4
26
w5
28
w7
29
w8
30
w9
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xbb3f3c…e046
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0xb82f494f…db33
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
10 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity