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.
e278c2f06e83ce26617d602582230d29ebedae9618e52bfa1060c96ddcc6c18b
Both payments are on their chains and locked to the same secret hash 39e03c96434f2225c3be6e30cf35e1f43e3db668, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e278c2f06e83ce26617d602582230d29ebedae9618e52bfa1060c96ddcc6c18b
- MakerPaymentSpent: 8d7104ee133eac57e6660c965e2432628d2d462a4bb988fdc17e8f5a9d49b799
99ba21e4458c2856bf4d00473aec656d1072f48bc0ee509da37e92c7754b6cdf
Both payments are on their chains and locked to the same secret hash 39e03c96434f2225c3be6e30cf35e1f43e3db668, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2116faa194fe7fc7279f55520492ff36aca10d235c0acfda5952726bca26bb9b
- TakerPaymentSent · TakerPaymentReceived: 99ba21e4458c2856bf4d00473aec656d1072f48bc0ee509da37e92c7754b6cdf
- TakerPaymentSpent: faac544571c8d89eb2e0a9d1c7b18368825cc52d1e73d93da382a4c344a7705c
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.