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 0.00 USDC deposited across 0 mints, the
assets word of the ERC-4626 events.•The shares held now convert to 0.000125 USDC, the vault’s
convertToAssets of this balance at block 52,878,291.•The share ledger adds up to the wei: 0.00 MMT minted plus 0.000109 MMT transferred in, less what was burned, is the 0.000109 MMT the vault’s
balanceOf reports at that block.•5 rows moved shares only; the bar values their shares at the vault’s share price at each block.
This address’s own events in the vault
5 rows at or below block 52,850,463 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,878,291.
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.000109 MMT and balanceOf at block 52,878,291 gives 0.000109, 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,878,291, not a convention this page assumed.
replayed from this address's own transfers
5 events
Transfers, 9 Jul 2025: 0.0001 MMT to the wallet
0.0001M
TransfersReceived0.000109281356464584 MMTM
10%performance fee
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.