Can anyone explain this transaction?


It features one input and, as outputs, includes the contract (script address) alongside the same address repeated five times, plus some reward withdrawals.

I created the contract (script) and its enterprise address to lock (or 'burn') tokens. I'm puzzled about how and why this transaction occurred.

You can observe dozens of standard transactions on the same script here:


This is the first time I've encountered such an odd transaction.

  • What's strange about it? The fact that it creates multiple UTxOs in the sender's wallet is an optimization for the parallelism of the future transactions. Commented Apr 29 at 7:56


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.