At block 52,874,257
1.63 USDCPClaim
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 5.00 USDC deposited across 4 mints and 4.01 USDC withdrawn across 3 burns, the
assets word of the ERC-4626 events.•The shares held now convert to 1.63 USDC, the vault’s
convertToAssets of this balance at block 52,874,257.•The share ledger adds up to the wei: 4.68 pUSDCy minted, less what was burned, is the 0.93 pUSDCy the vault’s
balanceOf reports at that block.This address’s own events in the vault
7 rows at or below block 52,850,463 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,874,257.
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.933531 pUSDCy and balanceOf at block 52,874,257 gives 0.933531, 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,874,257, not a convention this page assumed.
replayed from this address's own transfers
7 events
Withdrew, 13 Feb 2026
2.33: 2.5 USDC to the wallet, 2.33 pUSDCy into the position
2.5
2.33Withdrew
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, 13 Feb 20260.0982: 0.1052 USDC to the wallet, 0.0982 pUSDCy into the position
0.1052
0.0982Withdrew
Largest at this block: cbBTC, then cbETH.
6
Deposited, 13 Feb 20263: 3 USDC into the position, 2.8 pUSDCy to the wallet
2.8
3Deposited
Largest at this block: cbBTC, then Idle market.
5
Withdrew, 11 Feb 20261.32: 1.4 USDC to the wallet, 1.32 pUSDCy into the position
1.4
1.32Withdrew
All of this address's USDC claim sat in cbBTC at this block.
4
Deposited, 11 Feb 20261: 1 USDC into the position, 0.9415 pUSDCy to the wallet
0.9415
1Deposited
Largest at this block: cbBTC, then Idle market.
3
Deposited, 11 Feb 20260.5: 0.5 USDC into the position, 0.4708 pUSDCy to the wallet
0.4708
0.5Deposited
Largest at this block: cbBTC, then Idle market.
2
Deposited, 11 Feb 20260.5: 0.5 USDC into the position, 0.4708 pUSDCy to the wallet
0.4708
0.5Deposited
Largest at this block: cbBTC, then Idle market.
1
pUSDCyshare token symbol
PaperHands USDC Yieldshare 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.