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.
401abcadc6ba260c68c4c653a9550d02cbe3b2b5ec9df9fe81ca785e625369ee
Both payments are on their chains and locked to the same secret hash 5fa5d8f5e0cbd149edcd49533786304b13af1371, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 401abcadc6ba260c68c4c653a9550d02cbe3b2b5ec9df9fe81ca785e625369ee
a58294ff9be4d288649394b31ae3dcd1d2c8c5ccb90c2b76ec2bf43c3fbadc7b
Both payments are on their chains and locked to the same secret hash 5fa5d8f5e0cbd149edcd49533786304b13af1371, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 6a5151ffd4fc2cf259c20c1fd0c1ae91f8cab288e2fb84d54c0ea7a382da54cd
- TakerPaymentReceived: a58294ff9be4d288649394b31ae3dcd1d2c8c5ccb90c2b76ec2bf43c3fbadc7b
- TakerPaymentSpent: 048c7875d4f7f4e5efd334d469f0cb5cde612c30eb9595b5aa108223b527774d
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.