At block 52,876,387
0.000001 USDCTClaim
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.09 USDC deposited across 4 mints and 0.09 USDC withdrawn across 3 burns, the
assets word of the ERC-4626 events.•The shares held now convert to 0.000001 USDC, the vault’s
convertToAssets of this balance at block 52,876,387.•The share ledger adds up to the wei: 0.09 tbfUSDC minted, less what was burned, is the <0.000001 tbfUSDC the vault’s
balanceOf reports at that block.This address’s own events in the vault
7 rows at or below block 52,848,372 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,876,387.
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.000001 tbfUSDC and balanceOf at block 52,876,387 gives 0.000001, 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,876,387, not a convention this page assumed.
replayed from this address's own transfers
7 events
Deposited, 10 Sep 2026
0.000001: 0 USDC into the position, 0 tbfUSDC to the wallet
<0.000001
0.000001Deposited
All of this address's USDC claim sat in cbBTC 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.
7
Withdrew, 10 Sep 20260.0704: 0.0726 USDC to the wallet, 0.0704 tbfUSDC into the position
0.0726
0.0704Withdrew
Empty: this address held no shares at block 51,123,191, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
6
Withdrew, 31 Mar 20260.01: 0.0101 USDC to the wallet, 0.01 tbfUSDC into the position
0.0101
0.01Withdrew
Largest at this block: cbBTC, then cbETH.
5
Deposited, 30 Mar 20260.0615: 0.0615 USDC into the position, 0.0606 tbfUSDC to the wallet
0.0606
0.0615Deposited
Largest at this block: cbBTC, then cbETH.
4
Deposited, 27 Mar 20260.02: 0.02 USDC into the position, 0.0197 tbfUSDC to the wallet
0.0197
0.02Deposited
Largest at this block: cbBTC, then cbETH.
3
Withdrew, 25 Mar 20260.0099: 0.01 USDC to the wallet, 0.0099 tbfUSDC into the position
0.01
0.0099Withdrew
Empty: this address held no shares at block 43,827,021, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
2
Deposited, 10 Feb 20260.01: 0.01 USDC into the position, 0.0099 tbfUSDC to the wallet
0.0099
0.01Deposited
Largest at this block: cbBTC, then cbETH.
1
10%performance fee
tbfUSDCshare token symbol
bf testshare 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.