At close, 21 Jun '26
0 USDCClaim
Events
Reading the line…
These totals are summed over all 233 share movements in this address’s history in the vault.
•The vault’s events record 0.00 USDC deposited across 225 mints and 123.11 USDC withdrawn across 1 burn, the
assets word of the ERC-4626 events.•This address holds no shares at block 52,885,236, so no claim is stated.
•The share ledger adds up to the wei: 53.09 mvUSDC minted plus 6.43 mvUSDC transferred in, less what was burned, is the 0.00 mvUSDC the vault’s
balanceOf reports at that block.•7 rows moved shares only; the bar values their shares at the vault’s share price at each block.
•225 mint or burn carried no ERC-4626 event naming this address: it is in the share totals and in no asset total above, and the bar values its shares at the share price at its block.
This address’s own events in the vault
233 rows at or below block 52,845,686 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,885,236.
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 mvUSDC and balanceOf at block 52,885,236 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 6 plus a DECIMALS_OFFSET() of 12. Both are reads at block 52,885,236, not a convention this page assumed.
replayed from this address's own transfers
233 events
Withdrew, 21 Jun 2026
59.52: 123.11 USDC to the wallet, 59.52 mvUSDC into the position
123.11
59.52Withdrew
Empty: this address held no shares at block 47,634,431, 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.
233
Deposits, 3 Apr 2026 to 19 Jun 2026: 21.5 mvUSDC into the position
M21.5
DepositsMinted21.5M
0%performance fee
Transferred · from 0xf35b…b333, 20 Mar 2026: 4.89 mvUSDC Received
4.89
Transferredfrom0xf35b…b333
Largest at this block: cbBTC, then WETH. 2 more markets held the rest of this address's USDC claim.
187
Deposits, 3 Dec 2025 to 20 Mar 2026: 31.59 mvUSDC into the position
M31.59
DepositsMinted31.59M
Transfers, 22 Nov 2025 to 3 Dec 2025: 1.54 mvUSDC to the wallet
1.54M
TransfersReceived1.54M
5%performance fee
2%performance fee
mvUSDCshare token symbol
muscUSDCshare token symbol
Muscadine USDC Vaultshare token name
testingv1share token symbol
testingv1share token name
1%performance fee
muscadineV1USDCshare token symbol
Muscadine V1 USDC Vaultshare token name
muscadineUSDCshare token symbol
Muscadine USDC Vaultshare 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.