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.
a2301eeb7f905d05fcc507560f7565a28a825cacac2c0c320c7b410a6f9c0b23
Both payments are on their chains and locked to the same secret hash 6f0bea005d324d358f3e47bafe8380a2ccb6232e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a2301eeb7f905d05fcc507560f7565a28a825cacac2c0c320c7b410a6f9c0b23
- MakerPaymentSpent: 77bc65fe7eabc7bea059aab2955fab88f0c2644446e249f606a3e9c1b7e24afd
44d9ac57e0139886923b380a137b9f89b538761a79b781b8a1ceb29037b4cc07
Both payments are on their chains and locked to the same secret hash 6f0bea005d324d358f3e47bafe8380a2ccb6232e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 284e3c3a7da1e6ffa42306099f812734aa35ffa561c6b65bd624b4840a932906
- TakerPaymentSent · TakerPaymentReceived: 44d9ac57e0139886923b380a137b9f89b538761a79b781b8a1ceb29037b4cc07
- TakerPaymentSpent: 0f6315512c5210cd1afb74476b07b69577d02df6d01c5b4d565bcac457c4447d
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.