At close, 2 Feb '26
0 USDCClaim
Events
Reading the line…
These totals are summed over all 16 share movements in this address’s history in the vault.
•The vault’s events record 9.60 USDC deposited across 8 mints and 9.60 USDC withdrawn across 8 burns, the
assets word of the ERC-4626 events.•This address holds no shares at block 52,869,105, so no claim is stated.
•The share ledger adds up to the wei: 9.39 dForce USDC minted, less what was burned, is the 0.00 dForce USDC the vault’s
balanceOf reports at that block.This address’s own events in the vault
16 rows at or below block 52,850,676 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,869,105.
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 dForce USDC and balanceOf at block 52,869,105 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 52,869,105, not a convention this page assumed.
replayed from this address's own transfers
16 events
Withdrew, 2 Feb 2026
0.5868: 0.6002 USDC to the wallet, 0.5868 dForce USDC into the position
0.6002
0.5868Withdrew
Empty: this address held no shares at block 41,625,435, 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.
16
Withdrew, 2 Feb 20260.391: 0.4 USDC to the wallet, 0.391 dForce USDC into the position
0.4
0.391Withdrew
All of this address's USDC claim sat in cbBTC at this block.
15
Deposited, 2 Feb 20261: 1 USDC into the position, 0.9778 dForce USDC to the wallet
0.9778
1Deposited
All of this address's USDC claim sat in cbBTC at this block.
14
Withdrew, 2 Feb 20260.9779: 1 USDC to the wallet, 0.9779 dForce USDC into the position
1
0.9779Withdrew
Empty: this address held no shares at block 41,606,654, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
13
Deposited, 2 Feb 20261: 1 USDC into the position, 0.9779 dForce USDC to the wallet
0.9779
1Deposited
All of this address's USDC claim sat in cbBTC at this block.
12
Withdrew, 30 Jan 20261.17: 1.2 USDC to the wallet, 1.17 dForce USDC into the position
1.2
1.17Withdrew
Empty: this address held no shares at block 41,488,891, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
11
Deposited, 30 Jan 20261.2: 1.2 USDC into the position, 1.17 dForce USDC to the wallet
1.17
1.2Deposited
All of this address's USDC claim sat in cbBTC at this block.
10
Withdrew, 30 Jan 20261.17: 1.2 USDC to the wallet, 1.17 dForce USDC into the position
1.2
1.17Withdrew
Empty: this address held no shares at block 41,486,296, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
9
Deposited, 30 Jan 20261.2: 1.2 USDC into the position, 1.17 dForce USDC to the wallet
1.17
1.2Deposited
All of this address's USDC claim sat in cbBTC at this block.
8
Withdrew, 29 Jan 20262.15: 2.2 USDC to the wallet, 2.15 dForce USDC into the position
2.2
2.15Withdrew
Empty: this address held no shares at block 41,430,481, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
7
Deposited, 29 Jan 20262.2: 2.2 USDC into the position, 2.15 dForce USDC to the wallet
2.15
2.2Deposited
All of this address's USDC claim sat in cbBTC at this block.
6
Withdrew, 28 Jan 20261.96: 2 USDC to the wallet, 1.96 dForce USDC into the position
2
1.96Withdrew
Empty: this address held no shares at block 41,397,376, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
5
Deposited, 28 Jan 20261: 1 USDC into the position, 0.9782 dForce USDC to the wallet
0.9782
1Deposited
All of this address's USDC claim sat in cbBTC at this block.
4
Deposited, 26 Jan 20261: 1 USDC into the position, 0.9784 dForce USDC to the wallet
0.9784
1Deposited
All of this address's USDC claim sat in cbBTC at this block.
3
Withdrew, 26 Jan 20260.9789: 1 USDC to the wallet, 0.9789 dForce USDC into the position
1
0.9789Withdrew
Empty: this address held no shares at block 41,311,210, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
2
Deposited, 21 Jan 20261: 1 USDC into the position, 0.9789 dForce USDC to the wallet
0.9789
1Deposited
All of this address's USDC claim sat in cbBTC at this block.
1
5%performance fee
dForce USDCshare token symbol
dForce 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.