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.
0628d737905b634de978174de44f51b96b0dee46ef5a371412f03ff2c9c38ecd
Both payments are on their chains and locked to the same secret hash 159aa041d1db3d93ce9cedc12e5a3136039bece3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0628d737905b634de978174de44f51b96b0dee46ef5a371412f03ff2c9c38ecd
- MakerPaymentSpent: a9374f1decfcc2b4081ecacf238209db04391588aa1c581951b63ded44e596e2
e7ba57c5cede1114fd35905d7a1fe47100d6443ea045ccec3b30adff6ffb0b04
Both payments are on their chains and locked to the same secret hash 159aa041d1db3d93ce9cedc12e5a3136039bece3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d7ec0c9ce1f93048025a651d8c9910b1f4384b414427e87af8d562641a32d661
- TakerPaymentSent · TakerPaymentReceived: e7ba57c5cede1114fd35905d7a1fe47100d6443ea045ccec3b30adff6ffb0b04
- TakerPaymentSpent: ec25f380473db0b7a2d73103da97872487d660e78858c7a4634936c4c0c587df
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.