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.
4c6bee41afa0130a0e904b6078ffb0cd0080bd6520b224b5d709c45fa3821a9e
Both payments are on their chains and locked to the same secret hash 568b67809f2e6b42652afa4e8b9d686dc71b361a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4c6bee41afa0130a0e904b6078ffb0cd0080bd6520b224b5d709c45fa3821a9e
- MakerPaymentSpent: 5547516eec8d5478cdb50c8120351baa398722530b15eac05676cf8998a27975
924b9cd31fceaf627243d2977c918264879bab3100ef5e17fa55628bdfe724d0
Both payments are on their chains and locked to the same secret hash 568b67809f2e6b42652afa4e8b9d686dc71b361a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2fea9a50c4be1e6ae254d1019226c90cdcdc75da4a2921fa202ecba24f0ada9e
- TakerPaymentSent · TakerPaymentReceived: 924b9cd31fceaf627243d2977c918264879bab3100ef5e17fa55628bdfe724d0
- TakerPaymentSpent: 8d46214033e3b97cac4de0df6e10680bef01345655bba319cc5805347c64b818
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.