At close, 3 Jul '26
0 USDCClaim
Events
Reading the line…
These totals are summed over all 6 share movements in this address’s history in the vault.
•The vault’s events record 70.23 USDC deposited across 3 mints and 70.24 USDC withdrawn across 3 burns, the
assets word of the ERC-4626 events.•This address holds no shares at block 52,883,446, so no claim is stated.
•The share ledger adds up to the wei: 68.93 OUSDb-V1 minted, less what was burned, is the 0.00 OUSDb-V1 the vault’s
balanceOf reports at that block.This address’s own events in the vault
6 rows at or below block 52,852,974 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,883,446.
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 OUSDb-V1 and balanceOf at block 52,883,446 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,883,446, not a convention this page assumed.
replayed from this address's own transfers
6 events
Withdrew, 3 Jul 2026
26.51: 27.02 USDC to the wallet, 26.51 OUSDb-V1 into the position
27.02
26.51Withdrew
Empty: this address held no shares at block 48,152,206, 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.
6
Withdrew, 2 Jul 202626.51: 27.01 USDC to the wallet, 26.51 OUSDb-V1 into the position
27.01
26.51Withdrew
Largest at this block: cbXRP, then superOETHb. 4 more markets held the rest of this address's USDC claim.
5
Deposited, 2 Jul 202627.01: 27.01 USDC into the position, 26.51 OUSDb-V1 to the wallet
26.51
27.01Deposited
Largest at this block: cbXRP, then superOETHb. 4 more markets held the rest of this address's USDC claim.
4
Deposited, 2 Jul 202627.01: 27.01 USDC into the position, 26.51 OUSDb-V1 to the wallet
26.51
27.01Deposited
Largest at this block: cbXRP, then cbBTC. 2 more markets held the rest of this address's USDC claim.
3
Withdrew, 22 Jun 202615.92: 16.2 USDC to the wallet, 15.92 OUSDb-V1 into the position
16.2
15.92Withdrew
Empty: this address held no shares at block 47,675,724, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
2
Deposited, 22 Jun 202616.2: 16.2 USDC into the position, 15.92 OUSDb-V1 to the wallet
15.92
16.2Deposited
Largest at this block: cbXRP, then superOETHb. One more market held the rest of this address's USDC claim.
1
5%performance fee
OUSDb-V1share token symbol
OUSD Vault V1share 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.