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.
1cfa602423cb4e24ba318618e3913d2076ca62f76dfc505ccd137df0aaa72a59
Both payments are on their chains and locked to the same secret hash 779d0215d35c63478997f69f61fe56a738985d81, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1cfa602423cb4e24ba318618e3913d2076ca62f76dfc505ccd137df0aaa72a59
- MakerPaymentSpent: e9d637290ff4f95be9add925fe4f170c07f9a30dcfab785afe2e8a962de95e61
747d69ce27906f41ab92f438e1c073cace05a34eaf5a18d4522a5e029a562eeb
Both payments are on their chains and locked to the same secret hash 779d0215d35c63478997f69f61fe56a738985d81, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 66b07014ee401a4ac51a65a7cea06dac5ddfcac3fba396306379209835252434
- TakerPaymentSent · TakerPaymentReceived: 747d69ce27906f41ab92f438e1c073cace05a34eaf5a18d4522a5e029a562eeb
- TakerPaymentSpent: 6f15751beb663efee97002162312f817c04da7c38ff6c601e11b2f777d51b860
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.