withdraw() or redeem()At block 26,347,190
Reading the line…
These totals are summed over all 98 share movements in this address’s history in the vault.
assets word of the ERC-4626 events.convertToAssets of this balance at block 26,347,190.balanceOf reports at that block.98 rows at or below block 26,347,090 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 26,347,190.
Every share transfer this address sent or received on this vault, newest first, replayed into the balance the vault itself reports. The replay gives 10,373.477009 gtmsUSDc and balanceOf at block 26,347,190 gives 10,373.477009, 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,347,190, not a convention this page assumed.
Largest at this block: siUSD, then sUSDe. One more market held the rest of this address's msUSD claim.
Largest at this block: siUSD, then sUSDe.
Largest at this block: siUSD, then sUSDe.
Largest at this block: siUSD, then sUSDe.
Largest at this block: sUSDe, then siUSD.
Largest at this block: sUSDe, then siUSD.
All of this address's msUSD claim sat in sUSDe at this block.
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.