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.
6ddb82753b8164ad864b879270c207f8717a0ddb02c77da239926e84d60d5e6c
Both payments are on their chains and locked to the same secret hash 91496d2027c4961216bc98078fc0cb85ff14cd20, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6ddb82753b8164ad864b879270c207f8717a0ddb02c77da239926e84d60d5e6c
- MakerPaymentSpent: 5801bf0fedc2ffea692086cb3faf249fd0c41f8e35e61466357bfb08f3e9a47c
ed7460760911c438c81986368958de64a6f22372f5b7c067dd974e5ac7db1f12
Both payments are on their chains and locked to the same secret hash 91496d2027c4961216bc98078fc0cb85ff14cd20, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9925200606def016cc221db03332a1a69fa430d5c3c81cf855d1ad2dfcd556a5
- TakerPaymentSent · TakerPaymentReceived: ed7460760911c438c81986368958de64a6f22372f5b7c067dd974e5ac7db1f12
- TakerPaymentSpent: e2fc1f9f30a837191b25af75ef5d085629f774c466e996f884fae30892751140
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.