Same-block

Same block ordering can be extremely profitable in situations where the opportunity is only present within a single block. For example, a mint where the unlock opens the door to a valuable purchase at low cost, but becomes gas-prohibitive as soon as the next block comes.

In order for your transaction to achieve same-block ordering as another transaction, you need to describe the target transaction.

To be able to use Same-block scheduling, No-pending must be turned off in settings. This is so that Kekotron has access to the mempool. Make sure your node supports mempool filters. See the Setup section in this manual for details.

Kekotron gives you the option to describe the target transaction with multiple properties.

from - Transaction "from" field must be equal to. e.g. "0x299916F11Db0a2d3e00379b8a398cad68EFB436D"

to - Transaction "to" field must be equal to.

exact data - The full exact string of the "data" field must be equal to.

data begins with - The exact strings that the "data" field must begins with. e.g. "0xabc123"

data ends with - The exact strings that the "data" field must ends with. e.g. "00001"

data contains - An exact string that must be contained in the "data" field. e.g. "00000000000"

Once an transaction matching these criteria has been found in the mempool, a transaction(s) will be sent out with the exact same maxFeePerGas and maxPriorityFeePerGas, giving you a good chance to achieve same block ordering.

This does not guarantee that your transaction will be ordered after the target transaction within this block. For this reason you should send out your transaction from multiple wallets to be sure that one of them hits the correct ordering.

---

Example 1

In the example above, once any transaction from address "0xB0D1ED57b3C7a76F1733217A5B5696c4a52Ee713" is detected in the mempool, your prepared transaction will be sent out from 4 different wallets(1, 2, 3 and 4) and likely be ordered right after the target, within the same block.

Example 2

Once the Schedule button is pressed, entries are greyed out and can't be changed, until your trigger is met or you press Cancel

In this example, your prepared transaction will be sent out from two wallets(1 and 2) once the mempool contains a transaction that:

• is send to "0x0B4Fa82570d1B45a7eC40a8CCBd0409A3B51FC7e"

AND

• has a data field that begins with "0x75b34af3"

AND

• has a data field that ends with "0000000001"