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.
d52f8a34473f021bc62a8b2faea316524b3e7604fbaec3deace4265203481713
Both payments are on their chains and locked to the same secret hash 0dc4ff202167a88c085d36f1eea669e22265c083, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d52f8a34473f021bc62a8b2faea316524b3e7604fbaec3deace4265203481713
- MakerPaymentSpent: f9f8e0332d2b6300c90321e78c772e7f63d3b044f213332561e6ec7cb3c81675
87cc32266b230efd0d8260f90a7f5208f5e18863adb341d195659099ed1cefd5
Both payments are on their chains and locked to the same secret hash 0dc4ff202167a88c085d36f1eea669e22265c083, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 88229a13fa6969027a690793954c5d102328f12af07489209ffdeaf84792b5d0
- TakerPaymentSent · TakerPaymentReceived: 87cc32266b230efd0d8260f90a7f5208f5e18863adb341d195659099ed1cefd5
- TakerPaymentSpent: e1a3ff6e9fa7a34a855df4531e221a47da59c3561c717443cacbf2bd942990bc
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.