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.
19ade8792ce5672c115d156b18951ff4373e7313277a2c71020ef205400a6af2
Both payments are on their chains and locked to the same secret hash f4babae2db552b105492f1ac802c78d621103266, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 19ade8792ce5672c115d156b18951ff4373e7313277a2c71020ef205400a6af2
- MakerPaymentSpent: f98b4d5e3bbc8baa4fc1740ed3d0791c9813a01d78fbc7829f04e902ce321a58
f99a3ee2d22ff1b2f45abba4230b04ce86e14b4bd67cffaa4a8c975e4552a22d
Both payments are on their chains and locked to the same secret hash f4babae2db552b105492f1ac802c78d621103266, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b111b120779855b4694dfbecbb7a24acd68d275e509fd65854279205736b2179
- TakerPaymentSent · TakerPaymentReceived: f99a3ee2d22ff1b2f45abba4230b04ce86e14b4bd67cffaa4a8c975e4552a22d
- TakerPaymentSpent: dd80c4a29929858a6496da09a8af3d0c0868adccc0b3bd6d13dba1dfed3b0409
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.