At close, 27 Oct '25
0 MUSDClaim
Events
Reading the line…
These totals are summed over all 5 share movements in this address’s history in the vault.
•The vault’s events record 50.3K MUSD deposited across 3 mints and 50.3K MUSD withdrawn across 2 burns, the
assets word of the ERC-4626 events.•This address holds no shares at block 26,344,517, so no claim is stated.
•The share ledger adds up to the wei: 50.3K aMUSD minted, less what was burned, is the 0.00 aMUSD the vault’s
balanceOf reports at that block.This address’s own events in the vault
Every row read on this request; reconciled at block 26,344,517.
Every share transfer this address sent or received on this vault, newest first, replayed into the balance the vault itself reports. The replay gives 0 aMUSD and balanceOf at block 26,344,517 gives 0, so the two agree and the rows below are drawn. Each row states its own share price, read at the block that row happened in; no line is drawn between two of them, because nothing was read between them.
Every share price below is convertToAssets(10^18), the 18 being this vault’s own decimals() — its asset’s 18 plus a DECIMALS_OFFSET() of 0. Both are reads at block 26,344,517, not a convention this page assumed.
replayed from this address's own transfers
5 events
Withdrew, 27 Oct 2025: 6,316 MUSD to the wallet, 6,316 aMUSD into the position
6.3KM
A6.3K
Withdrew
Empty: this address held no shares at block 23,670,704, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
Each band is a read at that row’s own block, and nothing is drawn between two of them. The vault’s asset moved between these blocks at the curator’s own reallocations, which are not rows here and are not read at all; the space between two rows is this timeline’s ordinary gap and says nothing. A segment is proportional and not a trace of anyone’s money: it is this address’s shares over the whole supply, applied to what the vault supplied in that market, so two addresses holding equal shares hold equal segments whatever either deposited or when.
5
Withdrew, 30 Sep 2025: 44,010 MUSD to the wallet, 44,009 aMUSD into the position
44KM
A44K
Withdrew
Largest at this block: tBTC, then cbBTC.
4
aMUSDshare token symbol
Deposited, 25 Sep 2025: 19,080 MUSD into the position, 19,080 aMUSD to the wallet
19KA
M19K
Deposited
Largest at this block: tBTC, then cbBTC.
3
Deposited, 20 Sep 2025: 25,000 MUSD into the position, 25,000 aMUSD to the wallet
25KA
M25K
Deposited
Largest at this block: tBTC, then cbBTC.
2
Deposited, 20 Sep 2025: 6,245 MUSD into the position, 6,245 aMUSD to the wallet
6.2KA
M6.2K
Deposited
Largest at this block: tBTC, then cbBTC.
1
Alpha MUSDshare token name
10%performance fee
Alpha MUSD Vaultshare token name
alphaMUSDshare token symbol
Alpha MUSD Coreshare token name
The vault’s own accrual, and the curator’s reallocations, are rows nowhere here. A row is something this address did. What accrual did to the share price shows in each row’s own price figure, and nowhere else. A transaction that carried this address’s own leg very likely moved other shares too; only this address’s leg is stated.