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.
668c5234b5001d3add9802adf64b4de9750d41bf3c097c6039bbe108d01a885a
Both payments are on their chains and locked to the same secret hash 1767efc17370913f8914494095c40df548352b55, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 668c5234b5001d3add9802adf64b4de9750d41bf3c097c6039bbe108d01a885a
- MakerPaymentSpent: 456ced0cde757fe5348f210f36a8286346bf2b3f33a68da007c8962bb612a212
65a76f73504cfb45d7cceafd85ff5a5f39794c107a04deabd94d5ea5cabda4f8
Both payments are on their chains and locked to the same secret hash 1767efc17370913f8914494095c40df548352b55, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1a49aa0001ae507b98eda7925d3ca8b0f621e055dd280404ed4adc9d54d224b6
- TakerPaymentSent · TakerPaymentReceived: 65a76f73504cfb45d7cceafd85ff5a5f39794c107a04deabd94d5ea5cabda4f8
- TakerPaymentSpent: 0830abd4590dcec99bc4f2cb80406fdd00e8d6b2bff12c8f91065ab04e69ff3f
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.