withdraw() or redeem()At block 52,871,254
Reading the line…
These totals are summed over all 2,179 share movements in this address’s history in the vault.
assets word of the ERC-4626 events.convertToAssets of this balance at block 52,871,254.balanceOf reports at that block.2,179 rows at or below block 52,845,278 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,871,254.
Every share transfer this address sent or received on this vault, newest first, replayed into the balance the vault itself reports. The replay gives 4.834423 ionicUSDC and balanceOf at block 52,871,254 gives 4.834423, 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,871,254, not a convention this page assumed.
All of this address's USDC claim sat in cbBTC at this block.
The chain didn’t answer for where the vault’s asset sat at this block, so this row has no band. It shows once it does.
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.