At close, 5 Nov '25
0 LCAPClaim
Events
Reading the line…
These totals are summed over all 8 share movements in this address’s history in the vault.
•The vault’s events record 1.0K LCAP deposited across 3 mints and 7.82 LCAP withdrawn across 2 burns, the
assets word of the ERC-4626 events.•This address holds no shares at block 52,880,872, so no claim is stated.
•The share ledger adds up to the wei: 1.0K mLCAP minted plus 3.20 mLCAP transferred in, less what was burned and the 1.0K mLCAP transferred out, is the 0.00 mLCAP the vault’s
balanceOf reports at that block.•3 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
8 rows at or below block 52,844,893 from Rails's store of chain readings, 0 rows above it read now; reconciled at block 52,880,872.
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 mLCAP and balanceOf at block 52,880,872 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,880,872, not a convention this page assumed.
replayed from this address's own transfers
8 events
Withdrew, 5 Nov 2025
3.2: 3.2 LCAP to the wallet, 3.2 mLCAP into the position
3.2L
3.2Withdrew
Empty: this address held no shares at block 37,757,384, 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.
8
Transferred · from 0x6beb…bd62, 5 Nov 2025: 3.2 mLCAP Received
3.2
Transferredfrom0x6beb…bd62
Largest at this block: USDC, then WETH.
7
Transferred · to 0x6beb…bd62, 4 Nov 20253.2: 3.2 mLCAP Sent
Transferredto0x6beb…bd62
Empty: this address held no shares at block 37,748,884, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
6
Deposited, 4 Nov 2025: 3.2 LCAP into the position, 3.2 mLCAP to the wallet
3.2
L3.2
Deposited
Largest at this block: USDC, then WETH.
5
Withdrew, 4 Nov 20254.61: 4.62 LCAP to the wallet, 4.61 mLCAP into the position
4.62L
4.61Withdrew
Empty: this address held no shares at block 37,730,179, so nothing is attributed to any market. The vault's allocation at that block is in the panel below.
4
Transferred · to 0xada8…b4fa, 4 Nov 20251K: 1,000 mLCAP Sent
Transferredto0xada8…b4fa
Largest at this block: USDC, then WETH.
3
Deposited, 4 Nov 2025: 5.85 LCAP into the position, 5.85 mLCAP to the wallet
5.85
L5.85
Deposited
Largest at this block: USDC, then WETH.
2
Deposited, 4 Nov 2025: 1,000 LCAP into the position, 998.77 mLCAP to the wallet
998.77
L1K
Deposited
Largest at this block: USDC, then WETH.
1
10%performance fee
mLCAPshare token symbol
MEV Capital LCAP 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.