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.
5a1ea31c87ad79f2b50c68c8cdc60e7f0c68800feea73325b67956616573e94d
Both payments are on their chains and locked to the same secret hash 915208b55e49296570203133bccefb48fcd68485, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5a1ea31c87ad79f2b50c68c8cdc60e7f0c68800feea73325b67956616573e94d
- MakerPaymentSpent: eb02de87d9e937b0abf7fa4d4a0de8450c9be95ba00054afcea98efcf3ee59db
17616a09e4f6e48c84217d6a1fb8def325c0df67b4d87b9bcdc4e60d2fccf3b1
Both payments are on their chains and locked to the same secret hash 915208b55e49296570203133bccefb48fcd68485, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8a581b6e8ea86ea80a4bd798c8dfe87c153bbdac62ff084437ff1c379906b522
- TakerPaymentReceived · TakerPaymentSent: 17616a09e4f6e48c84217d6a1fb8def325c0df67b4d87b9bcdc4e60d2fccf3b1
- TakerPaymentSpent: e6ccfe0fcc97ef54bb39afadbb143595d95739f824b908fd9eca88c7664f1c6b
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.