> ## Documentation Index
> Fetch the complete documentation index at: https://dune-pro-1110-add-delete-endpoints-python-js-docs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# polkadot.extrinsics

> Description of Substrate extrinsics table on Dune.

export const TableSample = ({tableName, tableSchema}) => <div>
    <iframe src={`https://dune.com/embeds/3419983/5785629?table_schema_t6c1ea=${tableSchema}&table_name_t6c1ea=${tableName}`} style={{
  width: '100%',
  height: '500px',
  border: 'none',
  marginTop: '10px'
}} />
  </div>;

export const ColumnDescriptions = ({tableName, tableSchema}) => <div>
    <iframe src={`https://dune.com/embeds/3424601/5785601?table_name_t6c1ea=${tableName}&table_schema_t6c1ea=${tableSchema}`} style={{
  width: "100%",
  height: "500px",
  border: "none",
  marginTop: "10px"
}} />
    <Info> Datatypes on Snowflake datashare are different in some cases, read more <a href="/datashare/datashare#datatypes">here</a>.  </Info>
  </div>;

## Table description

Extrinsics (aka "transactions") normally contain a signature, some data to describe if the extrinsic has passed some validity checks and a reference to the pallet and call that it is intended for.  Extrinsics may be signed or unsigned.  Some extrinsics have a complex structure, e.g. when using proxy or utility pallets, resulting in the top-level call initiating other calls involving other pallets.

Common queries on the `extrinsics` table (e.g. `polkadot.extrinsics`) will typically filter on `block_time`, `section` and `method` and extract JSON encoded information in `data` or `decoded_data`.  In many cases, an initial query on the `extrinsics` table is best developed on the calls table instead to properly capture how users often use proxy and utility constructs to interact with the Substrate chain.

## Column Descriptions

<ColumnDescriptions tableSchema="polkadot" tableName="extrinsics" />

## Table Sample

<TableSample tableSchema="polkadot" tableName="extrinsics" />