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.
4473e7d67255ad4e591350b471edbfb2f7931e8f59b6b02d5b4828c5f2b85cab
Both payments are on their chains and locked to the same secret hash 2f1a8feda0afab41a81534ebe703bf3ebb27d59d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4473e7d67255ad4e591350b471edbfb2f7931e8f59b6b02d5b4828c5f2b85cab
- MakerPaymentSpent: db1ff4bab0e735f270db6de9ceeb73e6861744d008560422c8e3f63df0e53011
fa2cf1afc1c99c48ee45a1aac6c7a929cecf821d916a1db0394d7e02477e17fb
Both payments are on their chains and locked to the same secret hash 2f1a8feda0afab41a81534ebe703bf3ebb27d59d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7dbd9e6acc712b350dc2d32fd950950aa3ef6ef2bccd04749a4ff5d4c3141676
- TakerPaymentSent · TakerPaymentReceived: fa2cf1afc1c99c48ee45a1aac6c7a929cecf821d916a1db0394d7e02477e17fb
- TakerPaymentSpent: 098650a80f272e3e995c742cba3876c0139e396679decd1193889793de927a2f
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.