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.
ed728e86e392f5b989221c8bbf9a706e07fbd7e174f18d2ced4c131366e27309
Both payments are on their chains and locked to the same secret hash 8a1a6b00795e0241f85dff51af8d488e27f49e5f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ed728e86e392f5b989221c8bbf9a706e07fbd7e174f18d2ced4c131366e27309
- MakerPaymentSpent: f60b07ff9f268b3b16b69b349061705cc0b5c92f35369b65f55155fcf0d3775d
2006940365320cca77adb323b318391d557c793780264cf10fc14d40a1763c5e
Both payments are on their chains and locked to the same secret hash 8a1a6b00795e0241f85dff51af8d488e27f49e5f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5e277cbdf71c117a91387619a87736f1f2ccfc485a6062207c371b12058ba7a6
- TakerPaymentSent · TakerPaymentReceived: 2006940365320cca77adb323b318391d557c793780264cf10fc14d40a1763c5e
- TakerPaymentSpent: a387138a1e2377da698b20cd2a184e2bafded8db83309471d11446bcd84571de
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.