At block 52,874,174
18.5 USDCMClaim
Events
Reading the line…
These totals are summed over all 5 share movements in this address’s history in the vault.
•The vault’s events record 0.00 USDC deposited across 0 mints, the
assets word of the ERC-4626 events.•The shares held now convert to 18.50 USDC, the vault’s
convertToAssets of this balance at block 52,874,174.•The share ledger adds up to the wei: 0.00 mcUSDC minted plus 33.26 mcUSDC transferred in, less what was burned and the 17.00 mcUSDC transferred out, is the 16.26 mcUSDC the vault’s
balanceOf reports at that block.•5 rows moved shares only; the bar values their shares at the vault’s share price at each block.
This address’s own events in the vault
5 rows at or below block 52,848,183 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,874,174.
Every share transfer this address sent or received on this vault, newest first, replayed into the balance the vault itself reports. The replay gives 16.263588 mcUSDC and balanceOf at block 52,874,174 gives 16.263588, 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,174, not a convention this page assumed.
replayed from this address's own transfers
5 events
Transferred · from 0xce74…bb51, 22 Oct 2025: 15.46 mcUSDC Received
15.46
Transferredfrom0xce74…bb51
Largest at this block: TOSHI, then WMTX. 4 more markets held the rest of this address's USDC claim.
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.
5
Transferred · to 0xce74…bb51, 22 Oct 20258: 8 mcUSDC Sent
Transferredto0xce74…bb51
Largest at this block: TOSHI, then WMTX. 4 more markets held the rest of this address's USDC claim.
4
Transferred · from 0xce74…bb51, 21 Oct 2025: 8.13 mcUSDC Received
8.13
Transferredfrom0xce74…bb51
Largest at this block: TOSHI, then WMTX. 4 more markets held the rest of this address's USDC claim.
3
Transferred · to 0xce74…bb51, 20 Oct 20259: 9 mcUSDC Sent
Transferredto0xce74…bb51
Largest at this block: TOSHI, then WMTX. 4 more markets held the rest of this address's USDC claim.
2
Transferred · from 0xce74…bb51, 20 Oct 2025: 9.67 mcUSDC Received
9.67
Transferredfrom0xce74…bb51
Largest at this block: TOSHI, then WMTX. 4 more markets held the rest of this address's USDC claim.
1
mcUSDCshare token symbol
Macro USDC Vaultshare token name
15%performance fee
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.