Used as documented, the QueuingTransactionReceiptProcessor doesn't actually work... (or any other deferred receipt processor for that matter) https://github.com/web3j/web3j/issues/1207 It hands back a transaction receipt with only the transaction hash and attempting to access any other field will cause a unsupported operation to be thrown. This is correct as it's not waiting for the transaction to actually be mined and the queuing processor will asynchronously notify a callback when it is. However... All of the execution transaction methods that are used by the codegen'ed Java contract wrappers such as Sequencer call isStatusOK on the transaction receipt causing everything to go booooom. To work around we wrap the receipt processor and make the isStatusOk getter on the returned transaction receipt a little less boomy.