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.
13ae149f59ee0cfa0453588950fa95e8e571bf9aa7aa761fd09d745db90737ab
Both payments are on their chains and locked to the same secret hash 29ad28c8d447870bfdbf885b668db6025a972637, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 13ae149f59ee0cfa0453588950fa95e8e571bf9aa7aa761fd09d745db90737ab
- MakerPaymentSpent: e80d1a97d2de700bdf968a589c1dd741f9fd4e637295bdce7eee728d2a7a7013
0ea8651ce9dc788bd7db31c2e83de64ad4205b9b0c2dabd8e2ea7d536a8da345
Both payments are on their chains and locked to the same secret hash 29ad28c8d447870bfdbf885b668db6025a972637, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7ec94e70c5398dee6286055d1a10c231864be0a11070b41245e638acbe706102
- TakerPaymentSent · TakerPaymentReceived: 0ea8651ce9dc788bd7db31c2e83de64ad4205b9b0c2dabd8e2ea7d536a8da345
- TakerPaymentSpent: c2bb11d80d1c5348d7a2c21697670050dd0e569bf84d36ffec293bf9f87eb6d2
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.