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.
481ec0dd5cfc2344b16cffdf6d37ebbe0520d9399c315acfd10aa990aa203629
Both payments are on their chains and locked to the same secret hash e79edf859909df64e3280dd6a98c7e998d3841ff, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 481ec0dd5cfc2344b16cffdf6d37ebbe0520d9399c315acfd10aa990aa203629
- MakerPaymentSpent: 62d931ca91e37883e190295a2ccb30cf74e98407f60891009e91999e36d66911
605d74dc3f0c87e9e37b49bbbc1993eab6616684395643342f158f597f19f135
Both payments are on their chains and locked to the same secret hash e79edf859909df64e3280dd6a98c7e998d3841ff, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8974bf32ce376853099099294731ec75a20ef744cbbaa46fd705a4b269fd1682
- TakerPaymentSent · TakerPaymentReceived: 605d74dc3f0c87e9e37b49bbbc1993eab6616684395643342f158f597f19f135
- TakerPaymentSpent: 2901bc239647262f819e5c9ca1686019ab948827678d6f99632b3611383e3840
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.