At close, 7 Aug '25
0 USDCClaim
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 80.0K USDC deposited across 4 mints and 80.1K USDC withdrawn across 3 burns, the
assets word of the ERC-4626 events.•This address holds no shares at block 26,347,702, so no claim is stated.
•The share ledger adds up to the wei: 80.0K sweapUSDC minted, less what was burned, is the 0.00 sweapUSDC the vault’s
balanceOf reports at that block.This address’s own events in the vault
7 rows at or below block 26,346,962 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 26,347,702.
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 sweapUSDC and balanceOf at block 26,347,702 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 26,347,702, not a convention this page assumed.
replayed from this address's own transfers
7 events
Withdrew, 7 Aug 2025: 12.4 USDC to the wallet, 12.37 sweapUSDC into the position
12.4
S12.37
Withdrew
Empty: this address held no shares at block 23,092,352, 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.
7
Withdrew, 7 Aug 2025: 50,081 USDC to the wallet, 49,980 sweapUSDC into the position
50K
S50K
Withdrew
Largest at this block: EIGEN, then fxSAVE.
6
Deposited, 6 Aug 202530K: 30,000 USDC into the position, 29,975 sweapUSDC to the wallet
30KS
30KDeposited
Largest at this block: yUSD, then cUSDOUSDC. One more market held the rest of this address's USDC claim.
5
Withdrew, 6 Aug 2025: 30,006 USDC to the wallet, 29,982 sweapUSDC into the position
30K
S30K
Withdrew
Largest at this block: cUSDOUSDC, then mEDGE.
4
Deposited, 5 Aug 202515K: 15,003 USDC into the position, 15,000 sweapUSDC to the wallet
15KS
15KDeposited
Largest at this block: sUSDf, then cUSDOUSDC.
3
Deposited, 5 Aug 202530K: 30,000 USDC into the position, 30,000 sweapUSDC to the wallet
30KS
30KDeposited
All of this address's USDC claim sat in cUSDOUSDC at this block.
2
Deposited, 5 Aug 20255K: 5,000 USDC into the position, 5,000 sweapUSDC to the wallet
5KS
5KDeposited
All of this address's USDC claim sat in cUSDOUSDC at this block.
1
sweapUSDCshare token symbol
Secretweapon 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.