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.
e400acec74b064f52f30fb49b5ab922400e5260f8a4273acbe53cc764a5329a6
Both payments are on their chains and locked to the same secret hash ae85a7674491de07ead9332e19cb0f5e28fbc726, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e400acec74b064f52f30fb49b5ab922400e5260f8a4273acbe53cc764a5329a6
- MakerPaymentSpent: 0f5419cab8ff3cc5a5aae2fc84ab6e811ff4a467b720c7a1348ad8ea7ccd5306
305a5da657d923b56fe6706e6c5d7e3bbaa3fcb964e39b1dda61ca418b11a519
Both payments are on their chains and locked to the same secret hash ae85a7674491de07ead9332e19cb0f5e28fbc726, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c46e1cc14836b7cd18189bec4641f46cef5c54f9504084072507f59fe9c8f1ff
- TakerPaymentSent · TakerPaymentReceived: 305a5da657d923b56fe6706e6c5d7e3bbaa3fcb964e39b1dda61ca418b11a519
- TakerPaymentSpent: 38b0142309afb27b3a3b0a2f70a99a31078e8d2759ae1ed02c483268f0c72a8b
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.