Account Types on Smart Contract Chains

Entry last verified May 2026.

The two types

Property	Externally owned account	Contract account
Controlled by	A private key	Code
Can initiate a transaction	Yes	No, only in response
Has code	No	Yes
Has storage	No	Yes
Address derived from	The public key	The deployer and a counter

What follows

Only a key-controlled account can start a transaction. A contract executes when called; it cannot act spontaneously. Anything described as an automated on-chain process is triggered by someone sending a transaction.

A contract address can receive funds and may have no way to send them onward. Sending tokens to a contract address that does not handle them is a common and usually permanent error.

Contract accounts cannot be recovered by a phrase. They are controlled by their code, and if that code has no provision for recovery, none exists.

The account abstraction variant

Newer designs allow accounts that are contracts but can still initiate transactions through a separate mechanism.

That enables social recovery, spending limits, batched operations and fees paid by a third party. It costs more gas and introduces smart contract risk to your account itself.

Identifying which you are dealing with

A block explorer shows whether an address has code. An address with code is a contract.

This check takes ten seconds and it is worth doing before sending anything to an unfamiliar address, because the recovery position differs entirely.

The practical consequences

Verify the destination type for large transfers to addresses you have not used.

Understand that approvals are granted to contracts, which is why a contract compromised later can use a permission granted earlier.

Recognise that a contract cannot help you. There is no support desk and no key holder unless one was built in.

For ordinary use

Transfers between key-controlled accounts, and between a venue such as venues where the asset is listed for retail purchase and your own wallet, involve no contracts and none of these considerations.

The distinction matters once you interact with applications, which is the point at which the failure modes change from mistyped addresses to signed permissions.