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.
52a05f0ccd2552265b346d9d156db1a04e3223be5b2f81f7471c558acbd0c2d0
Both payments are on their chains and locked to the same secret hash e1b9629153c22e1bcbd77773310e3add83c626f1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 52a05f0ccd2552265b346d9d156db1a04e3223be5b2f81f7471c558acbd0c2d0
- MakerPaymentSpent: 061cd71341c3b90ada5faa5610be27c57a8aa0d180c936af100f237d215c247c
c62f561cd80a568ad73713638f688fa5f314492d234fc0ffdf866ce82ff752ea
Both payments are on their chains and locked to the same secret hash e1b9629153c22e1bcbd77773310e3add83c626f1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: efe9d0233a2ec591f7972e62c62eb6383fc5147ab658ced58172383d6aa27997
- TakerPaymentSent · TakerPaymentReceived: c62f561cd80a568ad73713638f688fa5f314492d234fc0ffdf866ce82ff752ea
- TakerPaymentSpent: 71e538b368cbfef141998591acf21f0047c09091003a5bf41c4340b8fcb94983
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.