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.
ff1564c71c72d10c865d4d0be9b37a4ea09c408a81905f5f161201829a042800
Both payments are on their chains and locked to the same secret hash 6a69582da9a93cb1943f9b9a6b4dbbd29d89497b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ff1564c71c72d10c865d4d0be9b37a4ea09c408a81905f5f161201829a042800
- MakerPaymentSpent: 99f948e16fd4159f8f036b5d862732883f8b95986754c1074aad3de592f4a21b
3982914d1786f6c3dcbd9c70cb01a81f9cea1b34d2ebf3a76fa4dd56a2761a96
Both payments are on their chains and locked to the same secret hash 6a69582da9a93cb1943f9b9a6b4dbbd29d89497b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5ed99652716d584f1d355882c081064ba26894769b28ad1cfa11d0b826cb81cb
- TakerPaymentSent · TakerPaymentReceived: 3982914d1786f6c3dcbd9c70cb01a81f9cea1b34d2ebf3a76fa4dd56a2761a96
- TakerPaymentSpent: 19891c1018013ae0156a168a39a9b8188b0fe056ffd8ed224531348dae7c32bd
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.