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.
0cae6f41a47c61c3c7f0e5a549cf494465efdb2dd768d73942f59bbc6de83aea
Both payments are on their chains and locked to the same secret hash 641908c00500a644ba196abf003dc4cd1de04423, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0cae6f41a47c61c3c7f0e5a549cf494465efdb2dd768d73942f59bbc6de83aea
- MakerPaymentSpent: d67b67c406f1312c0e7e8dd9821dd3f7c13dcb60c6ab2752995a185813a08135
daed562be6a7e2c8067c0eb5dd480de63d33fc1103e15f7c142d34433c7be526
Both payments are on their chains and locked to the same secret hash 641908c00500a644ba196abf003dc4cd1de04423, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 25f8983ff6ca73bd805d861cb75757d4664ea6acf9ed1f1efa61eecabbd8c4ea
- TakerPaymentSent · TakerPaymentReceived: daed562be6a7e2c8067c0eb5dd480de63d33fc1103e15f7c142d34433c7be526
- TakerPaymentSpent: 2c03449bbc3f971816c435cad076f0a89e931bc14ab551b117d01f89598bfbdd
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.