How can I debug exluded transactions?

Hi! I have a question about how transaction inclusion works in Flashbots Protect.

I sent a private transaction with a positive priority fee. It was targeted for three specific blocks. Later, I simulated the transaction at the end of each of those blocks, and it successfully executes in all of them. All three blocks had plenty of unused gas, so block fullness wasn’t a constraint.

However, the transaction was still not included, and the Flashbots API returned status: FAILED, isRevert: false, seenInMempool: false.

My question is:

Under what conditions would a private Flashbots Protect transaction be skipped even if it:

does not revert when appended to the actual block,

fits comfortably within the gas limit,

has a positive priority fee (so it gives the builder some revenue),

and I had the relevant builders selected in Protect?

Why builders may ignore low-value private transactions even when blocks have room?

Here’s an example in case it helps:

https://protect.flashbots.net/tx/0xff0d4cce391d5e49af5eb1e518a5c63d658c43c55151536eaa95a43125313b6d

In case no one knows, a pointer to some place I could ask this would be already helpful.

Thanks!

1 Like