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.
1fb35b13ad0d689d78495c32fd1ae5096ee17446e3a8f6b01c2ffe38f01e7d1a
Both payments are on their chains and locked to the same secret hash 3f82743f5e5ba1ae31c9687367d2aa7d917cf1a7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1fb35b13ad0d689d78495c32fd1ae5096ee17446e3a8f6b01c2ffe38f01e7d1a
- MakerPaymentSpent: 34a0bc553ee43ba1afaeb6d97289702e1103ab9fdfedfd604f624ad62e998b3f
e28ee153399519575ded9b07c9e06973968e5e3b5bc51bef8fae2a929c559f95
Both payments are on their chains and locked to the same secret hash 3f82743f5e5ba1ae31c9687367d2aa7d917cf1a7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c81ec23eda9dc4b74c7a4e97524b881845f83f0dfc43057b189b5f70e1c503fd
- TakerPaymentSent · TakerPaymentReceived: e28ee153399519575ded9b07c9e06973968e5e3b5bc51bef8fae2a929c559f95
- TakerPaymentSpent: a7165ddc65ccff4b74da4d74a2601142acea07f965db7b794857fe9850be4cfe
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.