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.
3cfd5ea50db67c36d0186016ddcee072ffb203a07cd79aeb6177a2ff67b5ff81
Both payments are on their chains and locked to the same secret hash 524067831002f6b2eaf4ed19b81c54f99890baf6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3cfd5ea50db67c36d0186016ddcee072ffb203a07cd79aeb6177a2ff67b5ff81
- MakerPaymentSpent: c9bf667da796554f8a358246bfc5bab69a4fc93669e355b87c6290287bcf389e
0dfd3758aa7a90dba2f5d358c242d8e5f68eb238a0b7254f7ea1a7e36d39629b
Both payments are on their chains and locked to the same secret hash 524067831002f6b2eaf4ed19b81c54f99890baf6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6af8b8247c2ae4ee729def81647b0e7bf31a006a3367fa53edfc5a2b419cddbd
- TakerPaymentSent · TakerPaymentReceived: 0dfd3758aa7a90dba2f5d358c242d8e5f68eb238a0b7254f7ea1a7e36d39629b
- TakerPaymentSpent: 2da29d624438fec213f518ce5b9ab525fc76a7782f4552dc998982dc9a6ac665
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.