An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
413b423e692631e03e7267a1d572b87ee7fbb90e22003e9fd6e820a4c0b9fab2
Both payments are on their chains and locked to the same secret hash a5fdadff4ce9bb75f1dbe383f9581738a49c3351, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 413b423e692631e03e7267a1d572b87ee7fbb90e22003e9fd6e820a4c0b9fab2
- MakerPaymentSpent: 605cc34aea4f36e637ef218974a39e3f544c5adecc4a5200d05a40f614567e90
2c6dcb528f45f1121f28ff205f41cee8f495cc0cec41cdff2d73d2fdeba3c3e1
Both payments are on their chains and locked to the same secret hash a5fdadff4ce9bb75f1dbe383f9581738a49c3351, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d5ced1f8fffef1c5b51f7626b5e1e9f98690a1cf04b1a4f2c18a87b3c0bfd756
- TakerPaymentSent · TakerPaymentReceived: 2c6dcb528f45f1121f28ff205f41cee8f495cc0cec41cdff2d73d2fdeba3c3e1
- TakerPaymentSpent: 6bd75b6ec1688d8133ff4f1acf9e899ef26c130b91f08be766aa289eb37670b0
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.