At block 52,871,630
108K USDCSClaim
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 912.5K USDC deposited across 4 mints and 850.0K USDC withdrawn across 2 burns, the
assets word of the ERC-4626 events.•The shares held now convert to 107.6K USDC, the vault’s
convertToAssets of this balance at block 52,871,630.•The share ledger adds up to the wei: 888.2K sparkUSDC minted, less what was burned, is the 99.3K sparkUSDC the vault’s
balanceOf reports at that block.This address’s own events in the vault
6 rows at or below block 52,845,848 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,871,630.
Every share transfer this address sent or received on this vault, newest first, replayed into the balance the vault itself reports. The replay gives 99,320.407683 sparkUSDC and balanceOf at block 52,871,630 gives 99,320.407683, 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,871,630, not a convention this page assumed.
replayed from this address's own transfers
6 events
Withdrew, 4 Sep 2026
649K: 700,000 USDC to the wallet, 649,477 sparkUSDC into the position
700K
649KWithdrew
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.
6
Withdrew, 21 Aug 2026139K: 150,000 USDC to the wallet, 139,379 sparkUSDC into the position
150K
139KWithdrew
All of this address's USDC claim sat in cbBTC at this block.
5
Deposited, 9 Oct 20254.9K: 4,892 USDC into the position, 4,713 sparkUSDC to the wallet
4.7K
4.9KDeposited
All of this address's USDC claim sat in cbBTC at this block.
4
Deposited, 25 Aug 2025206K: 205,509 USDC into the position, 199,431 sparkUSDC to the wallet
199K
206KDeposited
All of this address's USDC claim sat in cbBTC at this block.
3
Deposited, 1 Aug 2025702K: 702,000 USDC into the position, 683,954 sparkUSDC to the wallet
684K
702KDeposited
All of this address's USDC claim sat in cbBTC at this block.
2
Deposited, 1 Aug 202581.18: 81.18 USDC into the position, 79.09 sparkUSDC to the wallet
79.09
81.18Deposited
All of this address's USDC claim sat in cbBTC at this block.
1
10%performance fee
sparkUSDCshare token symbol
Spark USDC Vaultshare 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.