At close, 14 May '26
0 cbBTCClaim
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 3.13 cbBTC deposited across 3 mints and 3.13 cbBTC withdrawn across 1 burn, the
assets word of the ERC-4626 events.•This address holds no shares at block 52,876,148, so no claim is stated.
•The share ledger adds up to the wei: 3.13 mvcbBTC minted plus 0.0000921 mvcbBTC transferred in, less what was burned, is the 0.00 mvcbBTC the vault’s
balanceOf reports at that block.•1 row moved shares only; the bar values its shares at the vault’s share price at its block.
This address’s own events in the vault
5 rows at or below block 52,848,753 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,876,148.
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 mvcbBTC and balanceOf at block 52,876,148 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 8 plus a DECIMALS_OFFSET() of 10. Both are reads at block 52,876,148, not a convention this page assumed.
replayed from this address's own transfers
5 events
Withdrew, 14 May 2026
3.13: 3.13 cbBTC to the wallet, 3.13 mvcbBTC into the position
3.13
3.13Withdrew
Empty: this address held no shares at block 46,006,131, 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
Deposited, 1 Jan 20260.0275: 0.0275 cbBTC into the position, 0.0275 mvcbBTC to the wallet
0.0275
0.0275Deposited
Largest at this block: LBTC, then LBTC. One more market held the rest of this address's cbBTC claim.
4
Deposited, 21 Dec 20250.0002: 0.0002 cbBTC into the position, 0.0002 mvcbBTC to the wallet
0.0002
0.0002Deposited
Largest at this block: LBTC, then LBTC. One more market held the rest of this address's cbBTC claim.
3
Transferred · from 0xf2ea…6293, 14 Dec 2025: 0.0001 mvcbBTC Received
0.0001
Transferredfrom0xf2ea…6293
Largest at this block: LBTC, then LBTC. One more market held the rest of this address's cbBTC claim.
2
5%performance fee
Deposited, 6 Nov 20253.1: 3.1 cbBTC into the position, 3.1 mvcbBTC to the wallet
3.1
3.1Deposited
Largest at this block: LBTC, then Idle market.
1
2%performance fee
mvcbBTCshare token symbol
1%performance fee
muscadinecbBTCshare token symbol
Muscadine cbBTC 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.