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.
ce5a25cd1b0421bb832d6398b9b9a1cd64867738558668d661b44e26d9ab5f96
Both payments are on their chains and locked to the same secret hash 6f48f1241ed273d58c0d79a008b2615ddb6a3844, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ce5a25cd1b0421bb832d6398b9b9a1cd64867738558668d661b44e26d9ab5f96
- MakerPaymentSpent: 49ee6258f4eca5936da704d9d224b83f0ad1de55399531d162f6f4a18ce3b8a1
04059548a59a86cea48eb77c44e9c3cf02d256ac277051de1db6bef5713541e9
Both payments are on their chains and locked to the same secret hash 6f48f1241ed273d58c0d79a008b2615ddb6a3844, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c909e0c7f51d0393f5319283c4febaeef43b715816abe56f836f53ee834081ba
- TakerPaymentSent · TakerPaymentReceived: 04059548a59a86cea48eb77c44e9c3cf02d256ac277051de1db6bef5713541e9
- TakerPaymentSpent: 74deeaa753f4016e51429447d9fa5629e38df6870e28528c57d09fdf6ecfeafb
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.