At close, 7 Apr '25
0 sUSDSClaim
Events
Reading the line…
These totals are summed over all 9 share movements in this address’s history in the vault.
•The vault’s events record 18.8K sUSDS deposited across 5 mints and 18.8K sUSDS withdrawn across 4 burns, the
assets word of the ERC-4626 events.•This address holds no shares at block 52,887,143, so no claim is stated.
•The share ledger adds up to the wei: 18.8K gtSUSDSc minted, less what was burned, is the 0.00 gtSUSDSc the vault’s
balanceOf reports at that block.This address’s own events in the vault
9 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,887,143.
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 gtSUSDSc and balanceOf at block 52,887,143 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 18 plus a DECIMALS_OFFSET() of 0. Both are reads at block 52,887,143, not a convention this page assumed.
replayed from this address's own transfers
9 events
Withdrew, 7 Apr 2025
13K: 12,937 sUSDS to the wallet, 12,937 gtSUSDSc into the position
13K
13KWithdrew
Empty: this address held no shares at block 28,614,911, 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.
9
Withdrew, 1 Apr 20251,000: 1,000 sUSDS to the wallet, 1,000 gtSUSDSc into the position
1K
1,000Withdrew
All of this address's sUSDS claim sat in cbBTC at this block.
8
Withdrew, 1 Apr 20251,000: 1,000 sUSDS to the wallet, 1,000 gtSUSDSc into the position
1K
1,000Withdrew
All of this address's sUSDS claim sat in cbBTC at this block.
7
Deposited, 30 Mar 20255.7K: 5,740 sUSDS into the position, 5,740 gtSUSDSc to the wallet
5.7K
5.7KDeposited
All of this address's sUSDS claim sat in cbBTC at this block.
6
Deposited, 21 Mar 20259.2K: 9,196 sUSDS into the position, 9,196 gtSUSDSc to the wallet
9.2K
9.2KDeposited
All of this address's sUSDS claim sat in cbBTC at this block.
5
Withdrew, 21 Mar 20253.8K: 3,831 sUSDS to the wallet, 3,831 gtSUSDSc into the position
3.8K
3.8KWithdrew
Empty: this address held no shares at block 27,867,968, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
4
Deposited, 20 Mar 2025957.75: 957.75 sUSDS into the position, 957.75 gtSUSDSc to the wallet
957.75
957.75Deposited
All of this address's sUSDS claim sat in cbBTC at this block.
3
Deposited, 19 Mar 2025957.84: 957.84 sUSDS into the position, 957.84 gtSUSDSc to the wallet
957.84
957.84Deposited
All of this address's sUSDS claim sat in cbBTC at this block.
2
Deposited, 19 Mar 20251.9K: 1,916 sUSDS into the position, 1,916 gtSUSDSc to the wallet
1.9K
1.9KDeposited
All of this address's sUSDS claim sat in cbBTC at this block.
1
gtSUSDScshare token symbol
Gauntlet sUSDS Coreshare token name
share token symbol
share 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.