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.
94cba3f4a21249d4726bd068cbabb919a5f5ece7ebef8138f494b9041b5644bc
Both payments are on their chains and locked to the same secret hash 11ce71bbd05caece19ac8ce91342bd2f698d9b00, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 94cba3f4a21249d4726bd068cbabb919a5f5ece7ebef8138f494b9041b5644bc
- MakerPaymentSpent: d558adb5bb9082166ca035a58b893e3c85f06a77886434e60aa193cb291ff96f
e3c637a127060b50c0ffc08c654839e93e9cf0611c2019183aadcb19665ad8b3
Both payments are on their chains and locked to the same secret hash 11ce71bbd05caece19ac8ce91342bd2f698d9b00, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 864e8c5774bfc44a9c56b4991320cb61054888e7925e04dbee41d0483aa87c72
- TakerPaymentSent · TakerPaymentReceived: e3c637a127060b50c0ffc08c654839e93e9cf0611c2019183aadcb19665ad8b3
- TakerPaymentSpent: 2255a21540e580de6f03128188ebfbb389163dc534b366b1530eeda4d332ff17
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.