Data Logic

Current Version : MCDW v1.3

Blocks

Each block includes information about the version of the Starknet protocol used when creating the block, as defined by Starknet documentation.

This is stored in blocks.protocol_version

PROTOCOL_VERSIONMIN(BLOCK_NUMBER)MAX(BLOCK_NUMBER)

NULL

0

3798

0.9.1

3799

4882

0.10.0

4883

6569

0.10.1

6570

12267

0.10.2

12268

16574

0.10.3

16575

28612

0.11.0

28613

43850

0.11.0.2

43851

61393

0.11.1

61394

68095

0.11.2

68096

103128

0.12.0

103129

164900

0.12.1

164901

472643

0.12.2

194411

472643

0.12.3

472644

501513

0.13.0

501514

607877

0.13.1

607878

head

Transactions

Transaction Type & Version

Starknet supports the following types of transactions (TX_TYPE) and their corresponding versions (TX_VERSION), as defined in the official Starknet documentation

TypeDescriptionTX_TYPETX_VERSION*

INVOKE

Invokes an existing function in a contract.

0

0 1 3

L1_HANDLER

[DEPRECATED]

1

0

DEPLOY_ACCOUNT

Deploys new account contracts in smart wallets

2

0 3

DEPLOY

[DEPRECATED] Deploys new account contracts in smart wallets

3

0 1 2 3

DECLARE

Declares new contract classes, enabling new contract instances.

4

0 1 2 3

TypeCurrent versionDeprecated versionsUnsupported versions

0 -INVOKE

v3

v1, v0

N/A

4 - DECLARE

v3

v2, v1

v0

2 -DEPLOY_ACCOUNT

v3

v0

N/A

3 -DEPLOY

N/A

N/A

v0

1 -L1_HANDLER

N/A

N/A

v0

Depending on the transaction type and version, some columns will not be populated (NULL) or can have different mappings compared to the RPC endpoints.

TX_TYPETX_VERSIONFROM_ADDRESSTO_ADDRESS

0

0

0x

contract_address

0

1

sender_address

0x

0

3

sender_address

0x

1

0

0x

contract_address

2

0

0x

contract_address_salt

2

3

0x

contract_address_salt

3

0

0x

contract_address_salt

3

1

0x

contract_address_salt

4

0

0x...01

0x

4

1

sender_address

0x

4

2

sender_address

0x

4

3

sender_address

0x

Last updated