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.
939d37394ccfac1aea5537c4774b00f3f016799da287f98b4962293309c555c9
Both payments are on their chains and locked to the same secret hash 303cba777f60e4a7130224e7a3bdcc4f9dc3b53e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 939d37394ccfac1aea5537c4774b00f3f016799da287f98b4962293309c555c9
- MakerPaymentSpent: f112801dea9dbeec208a0668cfb2b5be6c855829c57b025defb1ebd595b83571
0777b2ae01b856bd52c2a9bd916d3c0c3b876349640fca6f911506370b8a142f
Both payments are on their chains and locked to the same secret hash 303cba777f60e4a7130224e7a3bdcc4f9dc3b53e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 15ebc04f8a8ae39d4eaea96548d4cf86796fe63a77cff074fdaee9fbc52b16b0
- TakerPaymentSent · TakerPaymentReceived: 0777b2ae01b856bd52c2a9bd916d3c0c3b876349640fca6f911506370b8a142f
- TakerPaymentSpent: 69f3e541fb788c5b365a5396bc22d7cea7d16a07db7533614aec3bf024adac6c
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.