Back to Home

PiggyBank

program
0xd01d0bdaa0bd...eee8952f09fd
FrontierContract #9,239Exact Bytecode MatchEdit this contract
Deployed February 19, 2016 (10 years ago)Block 1,026,739

A simple ETH piggy bank contract with deposit events, owner-only collect, and self-destruct. Uses a hardcoded instance ID (88) in deposit events to distinguish

Frontier EraVerified Source

Historical Significance

An early example of parameterized contract deployment on Ethereum, where identical contract logic was deployed multiple times with different hardcoded constants to create a multi-instance system. Represents the Frontier-era pattern of simple ETH custody contracts before more sophisticated vault and savings protocols emerged.

Context

Deployed in February 2016 during the Frontier era, compiled with Solidity v0.1.1, one of the earliest compiler versions. At this time, smart contracts were simple and developers frequently used suicide() for cleanup and .send() for ETH transfers. The contract is among Ethereum's first 10,000 deployed contracts.

Key Facts
Deployment Block
1,026,739
Deployment Date
Feb 19, 2016, 07:59 AM
Code Size
607.0 B
Gas at Deploy
187,085
Transactions by Year
2016200
201766

Description

A minimal ETH savings contract deployed on Feb 19, 2016 during the Frontier era. Anyone can deposit ETH by sending a transaction to the contract, which emits a Deposit event with the sender's address, a hardcoded instance ID, and the deposit amount. Only the contract owner (set at deployment) can withdraw the accumulated balance via collect() or destroy the contract via kill().

The contract follows a common Frontier-era pattern of simple ETH vaults with owner-only withdrawal. The hardcoded ID of 88 in the Deposit event suggests this is one instance of a system where multiple piggy bank contracts were deployed, each with a unique identifier, allowing an off-chain service to track deposits across all instances.

The deployer (0x42dA8a05CB7eD9A43572b5BA1B8F82A0a6E263DC) created multiple copies of this contract with different instance IDs. The contract received 200 transactions in 2016 and 66 in 2017.

Source Verified

SolidityExact bytecode match(607 bytes)
Compiler: soljson

soljson v0.1.1+commit.6ff4cd6, optimizer OFF. 543-byte runtime. Sourcify does not support v0.1.1 (minimum is v0.4.11).

Heuristic Analysis

The following characteristics were detected through bytecode analysis and may not be accurate.

Detected Type: program
Contains SELFDESTRUCT opcode

Bytecode Overview

Opcodes607
Unique Opcodes89
Jump Instructions18
Storage Operations8

External Links