0x2214…ee0d

This address’s own events in the vault

1 rows at or below block 54,409,909 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 54,787,583.

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.1 USDC and balanceOf at block 54,787,583 gives 0.1, 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 54,787,583, not a convention this page assumed.

replayed from this address's own transfers

1 eventDates

Display

0.1

0.1

Deposited10 Jun '25 02:58

All of this address's USDC claim sat in WETH at this block.

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.

Deposited · 10 Jun '25 02:58

1

USDCshare token symbol

TFT USDCshare 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.