OverviewWhat this address is, since when, and how it is doing.ActivityEverything that happened here — transactions, transfers, internal calls, state changes.StorageContract storage activity: slots written, who writes them, how deep the calls go.EventsThe event log this contract itself emitted, decoded where the ABI is known.HoldersWho holds this asset now, ranked by balance.PoolsDEX pools this asset trades in, and its recent volume.GraphMoney flow and structure around this address.
Aave V3 LBTC A TokenaEthLBTC
ContractThe address currently carries runtime code. Derived unambiguously from chain data.Had runtime codeRuntime code existed at this address at some point of its history. Derived unambiguously from chain data.Fungible tokenAn ERC-20 surface on the code that actually executes (decimals, symbol, name, totalSupply), at least one observed ERC-20 Transfer, and zero ERC-721/1155 events. Says what the interface is — not whether the token is legitimate. Derived unambiguously from chain data.Transfers state-backedThis token's Transfer events are backed by matching state changes in the issuer's storage. Derived unambiguously from chain data.
Acts as a A Token.
BalanceNative ETH balance of this address, valued at $2,280.97/ETH
0 ETH
Direct transactionsTop-level transactions to or from this address: sent 0 / received 148. Activity through internal calls, events or token transfers is not counted here.
148
State changesHow many times this address's own account state changed — balance, nonce or code
1
Fees paidTotal gas fees this address has paid as a sender, all time.
0 ETH
Timeline
First seenFirst block where this address appeared in on-chain state
Last activeNewest block across the activity streams the platform could consult, inbound included. Events 25,791,255 · Token transfers 25,791,255 · Internal transfers — none · Direct transactions 25,733,566
No active blacklistsChecked against known issuer blacklists — none currently lists this address
CapabilitiesStructural abilities of the code, derived by the platform from bytecode and storage analysis
UpgradeableDelegatecalls to an implementation read from storage — behavior can change while the address stays the sameProxy: unknownDetected proxy family; detection confidence is a metric of the analysis, not trust6 functionsDistinct function selectors found in the runtime bytecode
Relationships
StructuralLinks derived from on-chain deployment and code identity
Deployed byThe account that executed the CREATE — often a factory contractAave V3 Pool ConfiguratorOfficial — verified contract: Aave V3 Pool Configuratordeploy txblock 21,701,7582025-01-25 13:16 UTC
Origin (tx.from)The EOA that sent and paid for the deployment transaction0x476e...95690x476e1cd47944e6ec43b1fdae606c312544c79569
ImplementationThe implementation contract this proxy delegates toAave V3 Default A Token ImplOfficial — verified contract: Aave V3 Default A Token Implunknown+3 earlier
Same bytecodeContracts whose runtime bytecode is byte-identical to this oneused by 4 contracts