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.
3714526271a15a233fbfe1969b278ac7f0cc48f1a63485100a1ca632636a21c7
Both payments are on their chains and locked to the same secret hash 231f2b153bbd83eb3981beab088d926bb2003df4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3714526271a15a233fbfe1969b278ac7f0cc48f1a63485100a1ca632636a21c7
- MakerPaymentSpent: fe7f74f52136bce28d9aa7e11523a45177f2c161ca9004a85dd2c739ab339da7
ec28dfa875cb662bd6ec00f5a37658b99ec08e8b2399a1b8d66c492a8bdfd066
Both payments are on their chains and locked to the same secret hash 231f2b153bbd83eb3981beab088d926bb2003df4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c03ff0df80260b15b6bb65ba181d67341782f4c75ec3450f681737b2397ed888
- TakerPaymentSent · TakerPaymentReceived: ec28dfa875cb662bd6ec00f5a37658b99ec08e8b2399a1b8d66c492a8bdfd066
- TakerPaymentSpent: 0d6fe7ac93d86ec18d5b5bfc9629809cdd190ccbe14681ca48b9451e4a5a1654
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.