At block 52,885,469
0.149 cbBTCGClaim
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.60 cbBTC deposited across 4 mints, the
assets word of the ERC-4626 events.•The shares held now convert to 0.15 cbBTC, the vault’s
convertToAssets of this balance at block 52,885,469.•The share ledger adds up to the wei: 0.59 gtcbBTCc minted, less what was burned and the 0.45 gtcbBTCc transferred out, is the 0.15 gtcbBTCc the vault’s
balanceOf reports at that block.•3 rows moved shares only; the bar values their shares at the vault’s share price at each block.
This address’s own events in the vault
7 rows at or below block 52,848,949 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,885,469.
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.148422 gtcbBTCc and balanceOf at block 52,885,469 gives 0.148422, 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,885,469, not a convention this page assumed.
replayed from this address's own transfers
7 events
Deposited, 12 Oct 2026
0.1495: 0.1495 cbBTC into the position, 0.1484 gtcbBTCc to the wallet
0.1484
0.1495Deposited
Largest at this block: LBTC, then Idle market.
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
Transferred · to 0xaffd…2c31, 29 Sep 20260.1484: 0.1484 gtcbBTCc Sent
Transferredto0xaffd…2c31
Empty: this address held no shares at block 51,927,470, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
6
Deposited, 21 Sep 20260.1495: 0.1495 cbBTC into the position, 0.1484 gtcbBTCc to the wallet
0.1484
0.1495Deposited
Largest at this block: Idle market, then LBTC.
5
Transferred · to 0xaffd…2c31, 9 Sep 20260.1484: 0.1484 gtcbBTCc Sent
Transferredto0xaffd…2c31
Empty: this address held no shares at block 51,065,106, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
4
Deposited, 27 Aug 20260.1495: 0.1495 cbBTC into the position, 0.1484 gtcbBTCc to the wallet
0.1484
0.1495Deposited
Largest at this block: LBTC, then Idle market.
3
Transferred · to 0xaffd…2c31, 26 May 20260.1485: 0.1485 gtcbBTCc Sent
Transferredto0xaffd…2c31
Empty: this address held no shares at block 46,514,585, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
2
Deposited, 22 May 20260.1495: 0.1495 cbBTC into the position, 0.1485 gtcbBTCc to the wallet
0.1485
0.1495Deposited
All of this address's cbBTC claim sat in LBTC 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.