pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,496,706
← previous block
next block →
recent activity
Analyzing
Block #97,496,706
35 transactions · 29 stateful · 2026-08-20 01:38:35 UTC
Parallelism
86
/100
Blocked
55
%
Avg conflicts / tx
0.77
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,496,706
· 35 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x50a0b275
· blocks 2
#3
executePacked
#4
0x7b84f330
· blocks 1
#5
0xf8b1083e
#6
0xf8b1083e
#7
execute
#8
0xab083028
#10
execOrders
· blocks 3
#12
0x6c05cd2b
· blocks 1
#13
execOrder
· blocks 2
#15
0xe3a3c9cc
#18
0x0c7abd22
· blocks 2
#21
updateDataFeedsValuesPartial
#22
updateDataFeedsValuesPartial
#26
0x0c7abd22
#30
setData
#31
0x9f068e…c203
#32
0x59558d29
#2
executePacked
· blocks 2
#11
execOrders
#14
execOrder
· blocks 1
#16
0x5acec890
· blocks 3
#19
0x0c7abd22
· blocks 1
#34
0x7b84f330
#9
0xab083028
· blocks 2
#17
0x5acec890
· blocks 2
#20
0x0c7abd22
· blocks 1
#23
execFwdPositionOpsV2
· blocks 2
#33
0xf2eaccd1
#24
0x62be7533
#25
execFwdPositionOpsV2
· blocks 1
#28
batchUpdate
· blocks 1
#27
execFwdPositionOpsV2
#29
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
9
w2
10
w0
11
w1
12
w0
13
w0
14
w1
16
w1
17
w2
18
w0
19
w1
20
w2
23
w2
24
w3
25
w3
27
w4
28
w3
29
w4
33
w2
34
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0xa3c91855…d0df
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x83dff1de…a5e6
0xd32edf…ff58
5 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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity