At block 52,884,968
0.00000166 LBTCGClaim
Events
Reading the line…
These totals are summed over all 4 share movements in this address’s history in the vault.
•The vault’s events record 0.00000296 LBTC deposited across 3 mints and 0.0000013 LBTC withdrawn across 1 burn, the
assets word of the ERC-4626 events.•The shares held now convert to 0.00000166 LBTC, the vault’s
convertToAssets of this balance at block 52,884,968.•The share ledger adds up to the wei: 0.00000294 gtLBTCc minted, less what was burned, is the 0.00000165 gtLBTCc the vault’s
balanceOf reports at that block.This address’s own events in the vault
4 rows at or below block 52,850,271 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,884,968.
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.000002 gtLBTCc and balanceOf at block 52,884,968 gives 0.000002, 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 8 plus a DECIMALS_OFFSET() of 10. Both are reads at block 52,884,968, not a convention this page assumed.
replayed from this address's own transfers
4 events
Withdrew, 21 Apr 2026
0.00000129: 0 LBTC to the wallet, 0 gtLBTCc into the position
0.0000013
0.00000129Withdrew
All of this address's LBTC claim sat in Idle market 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.
4
Deposited, 21 Apr 2026<0.000001: 0 LBTC into the position, 0 gtLBTCc to the wallet
<0.000001
<0.000001Deposited
All of this address's LBTC claim sat in Idle market at this block.
3
Deposited, 20 Apr 2026<0.000001: 0 LBTC into the position, 0 gtLBTCc to the wallet
<0.000001
<0.000001Deposited
All of this address's LBTC claim sat in Idle market at this block.
2
Deposited, 17 Apr 20260.000002: 0 LBTC into the position, 0 gtLBTCc to the wallet
0.00000199
0.000002Deposited
All of this address's LBTC claim sat in Idle market at this block.
1
10%performance fee
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.