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.
530c0267f9e7be6d34938e41ce8b5c4994bc0197cc76aff0df16f5f40fec7759
Both payments are on their chains and locked to the same secret hash 49b7a41bf7abe46fc25c677d3e416b5575da568a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 530c0267f9e7be6d34938e41ce8b5c4994bc0197cc76aff0df16f5f40fec7759
- MakerPaymentSpent: c09ef68c6391161ca61d4a387013e0318e3dcf493a8dfead1b5abbd76ef4dceb
75a2c76d4c0bb5533dd57117d8f356d7668d179346c436216d6de73b332314a7
Both payments are on their chains and locked to the same secret hash 49b7a41bf7abe46fc25c677d3e416b5575da568a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 91c11439efef6ac4152ae398ab1a9d120440781593fe8924b0b47628f722bf5e
- TakerPaymentSent · TakerPaymentReceived: 75a2c76d4c0bb5533dd57117d8f356d7668d179346c436216d6de73b332314a7
- TakerPaymentSpent: ac9c5f4ff369c93a5f02afb239b90873847737ca6471a9cbe9c4ff5b827bf7e3
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.