At block 55,013,301
0.528 USDCTClaim
Events
Reading the line…
These totals are summed over all 7 share movements in this address’s history in the vault.
•The vault’s events record 0.65 USDC deposited across 4 mints and 0.15 USDC withdrawn across 3 burns, the
assets word of the ERC-4626 events.•The shares held now convert to 0.53 USDC, the vault’s
convertToAssets of this balance at block 55,013,301.•The share ledger adds up to the wei: 0.65 tUSDC minted, less what was burned, is the 0.50 tUSDC the vault’s
balanceOf reports at that block.This address’s own events in the vault
7 rows at or below block 54,398,447 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 55,013,301.
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.499296 tUSDC and balanceOf at block 55,013,301 gives 0.499296, 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 55,013,301, not a convention this page assumed.
replayed from this address's own transfers
7 events
Deposited, 16 Sep 2025
0.0003: 0.0003 USDC into the position, 0.0003 tUSDC to the wallet
0.0003T
0.0003Deposited
Largest at this block: cbBTC, then cbETH.
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.
7
Deposited, 15 Sep 20250.4: 0.4 USDC into the position, 0.3992 tUSDC to the wallet
0.3992T
0.4Deposited
Largest at this block: cbBTC, then cbETH.
6
Withdrew, 15 Sep 2025: 0.09 USDC to the wallet, 0.0898 tUSDC into the position
0.09
T0.0898
Withdrew
Largest at this block: cbBTC, then cbETH.
5
Withdrew, 15 Sep 2025: 0.0501 USDC to the wallet, 0.05 tUSDC into the position
0.0501
T0.05
Withdrew
Largest at this block: cbBTC, then cbETH.
4
Withdrew, 15 Sep 2025: 0.01 USDC to the wallet, 0.01 tUSDC into the position
0.01
T0.01
Withdrew
Largest at this block: cbBTC, then cbETH.
3
Deposited, 12 Sep 20250.15: 0.15 USDC into the position, 0.1498 tUSDC to the wallet
0.1498T
0.15Deposited
Largest at this block: cbBTC, then cbETH.
2
Deposited, 12 Sep 20250.1: 0.1 USDC into the position, 0.0999 tUSDC to the wallet
0.0999T
0.1Deposited
Largest at this block: cbBTC, then cbETH.
1
Test USDC Vaultshare token name
Test USDCshare token name
Lulo Test USDCshare token name
tUSDCshare token symbol
testUSDCshare 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.