At block 52,891,635
0.126 cbBTCGClaim
Events
Reading the line…
These totals are summed over all 96 share movements in this address’s history in the vault.
•The vault’s events record 0.13 cbBTC deposited across 96 mints, the
assets word of the ERC-4626 events.•The shares held now convert to 0.13 cbBTC, the vault’s
convertToAssets of this balance at block 52,891,635.•The share ledger adds up to the wei: 0.13 gtcbBTCc minted, less what was burned, is the 0.13 gtcbBTCc the vault’s
balanceOf reports at that block.This address’s own events in the vault
96 rows at or below block 52,850,865 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,891,635.
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.125238 gtcbBTCc and balanceOf at block 52,891,635 gives 0.125238, 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,891,635, not a convention this page assumed.
replayed from this address's own transfers
96 events
Deposits, 2 Jan 2026 to 17 Oct 2026
0.1261: 0.1252 gtcbBTCc into the position, 0.1261 cbBTC into the position
0.1261G0.1252
DepositsMinted0.1252GDeposited0.1261
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.