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.
a88bd9356d4f93d8b7179a8ca5d7e09a799f905c4683f46eb5867c460a6a2e34
Both payments are on their chains and locked to the same secret hash 8c5826da150ba8f831e37e480d21609767eab6e5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a88bd9356d4f93d8b7179a8ca5d7e09a799f905c4683f46eb5867c460a6a2e34
- MakerPaymentSpent: 8102139957efde8330845e738c35f0086a75a65632a6a02ffff66d1a1e29a10a
f3b5d4967bb589d5ac5bdccd23504a3e7e5c3b5b4da191c2dbdb21fb4fcf8e83
Both payments are on their chains and locked to the same secret hash 8c5826da150ba8f831e37e480d21609767eab6e5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0925a5f3202c79b3d7c832ad5f9a938af487737c7a530a99b6c0f474d43d4353
- TakerPaymentSent · TakerPaymentReceived: f3b5d4967bb589d5ac5bdccd23504a3e7e5c3b5b4da191c2dbdb21fb4fcf8e83
- TakerPaymentSpent: 68ffb0fc9192fa554e4cb66c28601e841e97869d6c1cf9e64ac3b400dc4b5a3e
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.