pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,087,069
← previous block
next block →
recent activity
Analyzing
Block #99,087,069
37 transactions · 28 stateful · 2026-08-25 16:11:14 UTC
Parallelism
81
/100
Blocked
50
%
Avg conflicts / tx
0.76
Longest chain
7
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,087,069
· 37 txs across 7 waves · depth 7
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
wave
w5
wave
w6
#0
syscallReward
#1
0xd524a9da
· blocks 4
#4
exactInputSingle
#5
0x05ee6a22
#6
0x41a8f47c
#10
0x0c7abd22
#11
0x4cb2db39
· blocks 1
#13
execPerpOps
#14
0x6cfade05
#15
execPerpOps
#16
updateDataFeedsValuesPartial
#17
0xe3a3c9cc
#18
execOrder
#19
0x62be7533
#20
execFwdPositionOpsV2
· blocks 3
#22
0x3f5c179b
#23
executeBatch
#27
postStateList
#28
0x6a8dbf1a
#29
setData
#30
0xe31ac3…7e88
#31
0xb6e484…0ad9
#36
execOrders
#2
0xf78cb219
· blocks 4
#12
0x59558d29
#21
execFwdPositionOpsV2
· blocks 2
#3
executePacked
· blocks 3
#25
execFwdPositionOpsV2
· blocks 1
#7
0xab083028
· blocks 3
#9
0xab083028
#32
execOrders
· blocks 3
#8
0xab083028
#24
0x3f5c179b
· blocks 1
#33
execOrders
· blocks 2
#26
batchUpdate
#34
execOrders
· blocks 1
#35
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w3
8
w4
9
w3
11
w0
12
w1
20
w0
21
w1
24
w4
25
w2
26
w5
32
w3
33
w4
34
w5
35
w6
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd08db6ee…a943
0x40c49f…2af0
6 touches
3 conflicts
0xd1203697…1ae0
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x41201361…2b7b
0x065c9d…c394
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: MarginAccount
10 conflicts on slot
0x889d5e90c7…59929a
Audit this contract →
← previous block
·
next block →
recent activity