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.
fd2b4c6684eafd99dd1746d1225fb054643f96dad337f367215d5062517f08fb
Both payments are on their chains and locked to the same secret hash 2c8f9c63ba8e993763d7490d35ff55ac5522a75d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: fd2b4c6684eafd99dd1746d1225fb054643f96dad337f367215d5062517f08fb
- MakerPaymentSpent: 31277a1eae8a97159c110cfd0295b2012cd7459ff6b5904031d6192153778981
f4acdebdddd21899d422250bf83dd6541f2f8c31034d21831583db9b31eccac2
Both payments are on their chains and locked to the same secret hash 2c8f9c63ba8e993763d7490d35ff55ac5522a75d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: eccb624fa3688599562bfdd97e5476beebbabe2d8808e6974ca8cda6344773ef
- TakerPaymentSent · TakerPaymentReceived: f4acdebdddd21899d422250bf83dd6541f2f8c31034d21831583db9b31eccac2
- TakerPaymentSpent: 28e52deb09542d1ac94a6902759dbd44d9e97598300d40cc729ba506b35fbcfc
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.