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.
2c2663dcbce722d649f461d3363513561fc8f91b10f8b85904c049f7527ec63b
Both payments are on their chains and locked to the same secret hash 6cb44bde67333efc04835391ce0570500ad84091, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2c2663dcbce722d649f461d3363513561fc8f91b10f8b85904c049f7527ec63b
- MakerPaymentSpent: 02a953f6eb66193d1b7a527a84708180229a4db6a5fe75b75c12af17336ed97b
412d8f6ab0cb0dd5b7775dd54d4b574cf2f897e33e5c50de027512fe54d0fab1
Both payments are on their chains and locked to the same secret hash 6cb44bde67333efc04835391ce0570500ad84091, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b6b0220884298579a981fc5f656b37c39a8cc176f9e9f71c7d84392002a51bd0
- TakerPaymentSent · TakerPaymentReceived: 412d8f6ab0cb0dd5b7775dd54d4b574cf2f897e33e5c50de027512fe54d0fab1
- TakerPaymentSpent: c9de996bca7f4824f18b9459960a46828b2ac8d47f1a501a8528e53623b3c3d5
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.