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.
5e6cc44c5b2e106da70aece606374f9b2fc21b9a9e38cdf2b4afd7461b94e322
Both payments are on their chains and locked to the same secret hash 5623ce8841ebdcbd386a3004f6676c320aa267d5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5e6cc44c5b2e106da70aece606374f9b2fc21b9a9e38cdf2b4afd7461b94e322
- MakerPaymentSpent: 909032d64af7d9f1d189c8aaed7045d086414bb54f4a7e551f6a545dda16eed7
5745721f5619390a01d79aaff34b1b32f06745038e0c4a13002ca93874374137
Both payments are on their chains and locked to the same secret hash 5623ce8841ebdcbd386a3004f6676c320aa267d5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1fa7c7face53bd61413268a500c91df5fe75ff65b4d009d483842f31d878749f
- TakerPaymentSent · TakerPaymentReceived: 5745721f5619390a01d79aaff34b1b32f06745038e0c4a13002ca93874374137
- TakerPaymentSpent: f1ad9c01b6599cff7d5bdff1d686fb51699b94df34d189c90ec6b7bf734646b4
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.