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.
cc7b6659acb7520030efab69123ddc6bb454ebceb4f30145e9e68397fa155054
Both payments are on their chains and locked to the same secret hash c55d05511a70b66646d9c9feb04ebfa6b906e459, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cc7b6659acb7520030efab69123ddc6bb454ebceb4f30145e9e68397fa155054
- MakerPaymentSpent: a5717a7f6f0f76eca16ca579fc5f7fd7ec6378df13055cdf873badea50b0b39e
8e56a253b850aa2188fa7cbd0ab79d865e162f1c1a5eb463ea3da0b32e4694ce
Both payments are on their chains and locked to the same secret hash c55d05511a70b66646d9c9feb04ebfa6b906e459, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7374bded2ec4ae0b031c0c1526c03329083bbe6c5c2586022a2264a20849618e
- TakerPaymentSent · TakerPaymentReceived: 8e56a253b850aa2188fa7cbd0ab79d865e162f1c1a5eb463ea3da0b32e4694ce
- TakerPaymentSpent: 1026c1a609dfffb22b9600d35df40dbc763cd32c34145279efb838608db16161
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.