At block 52,869,104
1.9K USDCLClaim
Events
Reading the line…
These totals are summed over all 8 share movements in this address’s history in the vault.
•The vault’s events record 2.4K USDC deposited across 6 mints and 2.4K USDC withdrawn across 2 burns, the
assets word of the ERC-4626 events.•The shares held now convert to 1.9K USDC, the vault’s
convertToAssets of this balance at block 52,869,104.•The share ledger adds up to the wei: 2.4K lfUSDC minted, less what was burned, is the 38.69 lfUSDC the vault’s
balanceOf reports at that block.This address’s own events in the vault
8 rows at or below block 52,852,007 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,869,104.
Every share transfer this address sent or received on this vault, newest first, replayed into the balance the vault itself reports. The replay gives 38.690651 lfUSDC and balanceOf at block 52,869,104 gives 38.690651, 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,869,104, not a convention this page assumed.
replayed from this address's own transfers
8 events
Withdrew, 7 Aug 2025
2.4K: 2,395 USDC to the wallet, 2,374 lfUSDC into the position
2.4K
2.4KWithdrew
All of this address's USDC claim sat in RLP 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.
8
Deposited, 10 Jul 2025395: 395 USDC into the position, 394.13 lfUSDC to the wallet
394.13
395Deposited
Largest at this block: RLP, then cbBTC. One more market held the rest of this address's USDC claim.
7
Deposited, 2 Jul 20252K: 1,999 USDC into the position, 1,997 lfUSDC to the wallet
2K
2KDeposited
Largest at this block: cbBTC, then cbETH.
6
Deposited, 2 Jul 20251: 1 USDC into the position, 0.9988 lfUSDC to the wallet
0.9988
1Deposited
Largest at this block: cbETH, then cbBTC.
5
Deposited, 2 Jul 202511: 11 USDC into the position, 10.99 lfUSDC to the wallet
10.99
11Deposited
Largest at this block: cbETH, then cbBTC. One more market held the rest of this address's USDC claim.
4
Withdrew, 2 Jul 20250.9988: 1 USDC to the wallet, 0.9988 lfUSDC into the position
1
0.9988Withdrew
Largest at this block: cbETH, then cbBTC. One more market held the rest of this address's USDC claim.
3
Deposited, 2 Jul 20251: 1 USDC into the position, 0.9988 lfUSDC to the wallet
0.9988
1Deposited
Largest at this block: cbETH, then cbBTC. One more market held the rest of this address's USDC claim.
2
Deposited, 2 Jul 202510: 10 USDC into the position, 9.99 lfUSDC to the wallet
9.99
10Deposited
Largest at this block: cbETH, then cbBTC. One more market held the rest of this address's USDC claim.
1
7%performance fee
lfUSDCshare token symbol
Landforge Premier 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.