At close, 30 Dec '25
0 USDCClaim
Events
Reading the line…
These totals are summed over all 6 share movements in this address’s history in the vault.
•The vault’s events record 3.17 USDC deposited across 3 mints and 3.17 USDC withdrawn across 3 burns, the
assets word of the ERC-4626 events.•This address holds no shares at block 54,783,023, so no claim is stated.
•The share ledger adds up to the wei: 3.17 LightningUSDC minted, less what was burned, is the 0.00 LightningUSDC the vault’s
balanceOf reports at that block.This address’s own events in the vault
6 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,783,023.
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 LightningUSDC and balanceOf at block 54,783,023 gives 0, 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,783,023, not a convention this page assumed.
replayed from this address's own transfers
6 events
Withdrew, 30 Dec 2025: 1.17 USDC to the wallet, 1.17 LightningUSDC into the position
1.17
L1.17
Withdrew
Empty: this address held no shares at block 40,132,019, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
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.
6
Deposited, 29 Dec 20251.17: 1.17 USDC into the position, 1.17 LightningUSDC to the wallet
1.17L
1.17Deposited
Largest at this block: cbBTC, then wstETH.
5
Withdrew, 29 Dec 2025: 1 USDC to the wallet, 0.9992 LightningUSDC into the position
1
L0.9992
Withdrew
Empty: this address held no shares at block 40,128,563, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
4
Deposited, 29 Dec 20251: 1 USDC into the position, 0.9992 LightningUSDC to the wallet
0.9992L
1Deposited
Largest at this block: cbBTC, then wstETH.
3
Withdrew, 29 Dec 2025: 1 USDC to the wallet, 0.9992 LightningUSDC into the position
1
L0.9992
Withdrew
Empty: this address held no shares at block 40,128,517, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
2
Deposited, 29 Dec 20251: 1 USDC into the position, 0.9992 LightningUSDC to the wallet
0.9992L
1Deposited
Largest at this block: cbBTC, then wstETH.
1
LightningUSDCshare token symbol
Lightning 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.