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.
08e43dc1c433c6074e8fcaa4ceac279152979d8ddf01b6da2e759f69b8ca585a
Both payments are on their chains and locked to the same secret hash a1810b41cf790c4cb17f983796b49cd3df83a464, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 08e43dc1c433c6074e8fcaa4ceac279152979d8ddf01b6da2e759f69b8ca585a
- MakerPaymentSpent: 9c3ce25eb25067a8018e72ede2d3686ab2c73d3a0351b40d29aaa7fb1080a2b7
ec05ddec7b84e6783d41866b79cc880d1415726ae7f4954538275cacd7869b95
Both payments are on their chains and locked to the same secret hash a1810b41cf790c4cb17f983796b49cd3df83a464, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9642c716a95664e19d91efffde2f977d3e2fc26576a3c50ddf92dd466c6db69d
- TakerPaymentSent · TakerPaymentReceived: ec05ddec7b84e6783d41866b79cc880d1415726ae7f4954538275cacd7869b95
- TakerPaymentSpent: 39fedcb3eb4ed8f04a68135fd51331e20143897fbcf3b56f6f9b37f6d35ebd49
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.