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.
3d77ea7296607b29632f7db67c7d3d9aa77720149aeec49c540ff93fd768a37f
Both payments are on their chains and locked to the same secret hash f66bce828b5b7e7940fcd592845380266036af38, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3d77ea7296607b29632f7db67c7d3d9aa77720149aeec49c540ff93fd768a37f
- MakerPaymentSpent: a55758602c660fb16edcc4e96aa4c5bf3d3011bc8b6fe67f544d40304850539c
a397728faf70aa97e53c881ee863b2fea74456eaf3aacdaf47b32c641122f373
Both payments are on their chains and locked to the same secret hash f66bce828b5b7e7940fcd592845380266036af38, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d1ec3213b74d987f9d438be28009bc4197d21b16deee15ad78746b4e8552ecb2
- TakerPaymentSent · TakerPaymentReceived: a397728faf70aa97e53c881ee863b2fea74456eaf3aacdaf47b32c641122f373
- TakerPaymentSpent: cbd173b0443e41cf3aaff720b3d400f7ef142908dcbedcc7ae6d3e1afa9321db
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.