pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,909,975
← previous block
next block →
recent activity
Analyzing
Block #97,909,975
35 transactions · 31 stateful · 2026-08-21 12:40:31 UTC
Parallelism
77
/100
Blocked
48
%
Avg conflicts / tx
1
Longest chain
8
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,909,975
· 35 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
0x0c7abd22
· blocks 4
#2
0x6ad2e98b
#3
0xab083028
· blocks 3
#5
0xab083028
#6
execOrders
· blocks 4
#9
updateDataFeedsValuesPartial
#11
execFwdPositionOpsV2
· blocks 3
#13
execFwdPositionOpsV2
· blocks 2
#14
0x3f5c179b
#15
executeBatch
#21
execOrders
#22
forward
#23
setData
· blocks 1
#25
0x61d59c2d
#26
0x59558d29
#27
0x59558d29
#28
0x4cb2db39
#29
execOrders
#34
execOrders
#4
0xab083028
· blocks 1
#7
0x5acec890
· blocks 4
#16
0x3f5c179b
· blocks 1
#24
setData
#30
execOrders
· blocks 3
#8
0x928e4afa
· blocks 1
#10
execFwdPositionOpsV2
· blocks 3
#17
0x3f5c179b
#19
batchUpdate
#12
execFwdPositionOpsV2
· blocks 1
#20
execFwdPositionOpsV2
#18
execFwdPositionOpsV2
· blocks 1
#31
execOrders
· blocks 2
#32
execOrders
· blocks 1
#33
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
6
w0
7
w1
8
w2
10
w2
11
w0
12
w3
13
w0
16
w1
17
w2
18
w4
19
w2
20
w3
30
w1
31
w5
32
w6
- 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
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
6 touches
3 conflicts
0x4e359fa6…aea5
0x40c49f…2af0
6 touches
3 conflicts
0x3d5ea7c6…c774
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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