At block 26,347,116
0.116 PYUSDKClaim
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 139.2K PYUSD deposited across 4 mints and 139.2K PYUSD withdrawn across 2 burns, the
assets word of the ERC-4626 events.•The shares held now convert to 0.12 PYUSD, the vault’s
convertToAssets of this balance at block 26,347,116.•The share ledger adds up to the wei: 139.0K KdPYUSD minted, less what was burned, is the 0.11 KdPYUSD the vault’s
balanceOf reports at that block.This address’s own events in the vault
6 rows at or below block 26,347,026 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 26,347,116.
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.11263 KdPYUSD and balanceOf at block 26,347,116 gives 0.11263, 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,116, not a convention this page assumed.
replayed from this address's own transfers
6 events
Withdrew, 29 Dec 2025: 50,110 PYUSD to the wallet, 49,991 KdPYUSD into the position
50K
K50K
Withdrew
All of this address's PYUSD 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
Deposited, 26 Dec 202550K: 50,089 PYUSD into the position, 49,990 KdPYUSD to the wallet
50KK
50KDeposited
Largest at this block: Idle market, then wstETH.
5
Withdrew, 19 Dec 2025: 89,126 PYUSD to the wallet, 89,038 KdPYUSD into the position
89K
K89K
Withdrew
All of this address's PYUSD claim sat in wstETH at this block.
4
Deposited, 18 Dec 202539K: 39,028 PYUSD into the position, 38,995 KdPYUSD to the wallet
39KK
39KDeposited
Largest at this block: Idle market, then PAXG. 2 more markets held the rest of this address's PYUSD claim.
3
Deposited, 12 Dec 202550K: 50,043 PYUSD into the position, 50,042 KdPYUSD to the wallet
50KK
50KDeposited
Largest at this block: Idle market, then WBTC. 2 more markets held the rest of this address's PYUSD claim.
2
Deposited, 12 Dec 20253: 3 PYUSD into the position, 3 KdPYUSD to the wallet
3K
3Deposited
All of this address's PYUSD claim sat in Idle market at this block.
1
KdPYUSDshare token symbol
Kedao PYUSD 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.