Skip to main content

Table description

The aptos.signatures table documents the signatures associated with transactions on the Aptos blockchain. Signatures are critical for securing transactions, proving the identity of the sender, and ensuring data integrity. This table includes the signature type, data, and the transaction it authenticates, offering insights into the security mechanisms at play.

Table Schema

ColumnTypeDescription
block_heightBIGINTSequential number identifying the block’s position in the chain
block_dateDATEDate of the block for daily aggregations
block_timeTIMESTAMPTimestamp when the block was committed
block_hashVARBINARYUnique cryptographic hash identifying the block
block_first_versionUINT256First transaction version included in the block
block_last_versionUINT256Last transaction version included in the block
block_proposerVARBINARYAddress of the validator that proposed the block
block_roundUINT256Consensus round number for the block
block_epochUINT256Epoch number during which the block was created
block_metadata_idVARBINARYUnique identifier for the block metadata event
block_failed_proposer_indicesARRAY(INTEGER)Indices of validators that failed to propose before this block
block_previous_block_votes_bitvecARRAY(SMALLINT)Bit vector of validator votes on the previous block
tx_indexINTEGERPosition of the transaction within the block
tx_typeVARCHARType of the transaction (e.g. user_transaction, block_metadata)
tx_hashVARBINARYUnique hash identifying the transaction
tx_versionUINT256Global sequential version number of the transaction
tx_gas_usedUINT256Amount of gas consumed by the transaction
tx_vm_statusVARCHARDetailed status message returned by the Move VM
tx_successBOOLEANWhether the transaction executed successfully
tx_state_change_hashVARBINARYHash of all state changes produced by the transaction
tx_event_root_hashVARBINARYMerkle root hash of all events emitted by the transaction
tx_state_checkpoint_hashVARBINARYHash of the state checkpoint after this transaction
tx_accumulator_root_hashVARBINARYRoot hash of the transaction accumulator after this transaction
tx_timestampUINT256Unix timestamp of the transaction in microseconds
tx_senderVARBINARYAddress of the account that submitted the transaction
tx_max_gas_amountUINT256Maximum gas units the sender is willing to pay
tx_gas_unit_priceUINT256Price per gas unit in octas (1 APT = 10^8 octas)
tx_sequence_numberUINT256Sender’s account sequence number at the time of this transaction
tx_expiration_timestamp_secsUINT256Unix timestamp (seconds) after which the transaction expires
typeVARCHARTop-level signature scheme type (e.g. ed25519, multi_ed25519, multi_agent)
signer_typeVARCHARRole of the signer (e.g. sender, secondary_signer, fee_payer)
signer_signature_typeVARCHARCryptographic algorithm used by this signer (e.g. ed25519, secp256k1_ecdsa)
is_single_senderBOOLEANWhether the transaction has a single sender (as opposed to multi-agent)
signer_addressVARBINARYAddress of this particular signer
secondary_signer_indexINTEGERIndex of this signer among secondary signers (-1 for primary sender)
public_keyVARBINARYPublic key used to create the signature
signatureVARBINARYCryptographic signature bytes
bitmapVARBINARYBitmap indicating which keys signed in a multi-key scheme
bitmap_public_key_indexINTEGERIndex of this public key within the bitmap
thresholdBIGINTMinimum number of signatures required for multi-key authentication

Table Sample