set_max_pending_extrinsics_number
Call v401 → current New #3Set the maximum number of pending extrinsics allowed in the queue.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with set_max_pending_extrinsics_number, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch, and finally post-dispatch where ExtrinsicSuccess is emitted and fees are settled.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click items to navigate. Pan and zoom to explore.
From Chain Metadata
Set the maximum number of pending extrinsics allowed in the queue.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | value | u32 | value (u32) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Caller authorized to make changes
Effects
Postconditions
- Value successfully updated
Code Examples
import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";
const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });
// Build set_max_pending_extrinsics_number call
const value = 0;
const call = api.tx[stringCamelCase("MevShield")][stringCamelCase("set_max_pending_extrinsics_number")](
value
);Runtime Info
View Source- Pallet Index
- 30
- Call Index
- 3
- First Version
- v401
- Current Version
- v401