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.
19da0a25b640278b2acfd1f84477644c74e28eec2a7966d8e8ef0e2003e2eda8
Both payments are on their chains and locked to the same secret hash 4617887da0690f929bdc5a324ee650c95754fae8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 19da0a25b640278b2acfd1f84477644c74e28eec2a7966d8e8ef0e2003e2eda8
- MakerPaymentSpent: e60fb18f340e66ab5397e556064a5b347773918fee334ef8bc3f83c3e9e6be0d
7f92447edf297e27a9c8e5c07c263125b32732ea902d0acdd5a7f4c6e0269ac5
Both payments are on their chains and locked to the same secret hash 4617887da0690f929bdc5a324ee650c95754fae8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 804c55d4ec6ef5fd507513bb44d689c3be5be2c7dd9b0a7bbf1b58a4f45d1165
- TakerPaymentSent · TakerPaymentReceived: 7f92447edf297e27a9c8e5c07c263125b32732ea902d0acdd5a7f4c6e0269ac5
- TakerPaymentSpent: 3f2cbf1e5caa5bdbbbe7dee3b1baf0bff2ecb8258c4fb437d05a57f4849f71b7
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.