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.
c1277c0e478fd2bde8d6472536d87f42a55dcbb1d9ad5b8785f666bb07841503
Both payments are on their chains and locked to the same secret hash 4e371a89d7a04c3a1d9128571cf1155cc96eb4d5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: c1277c0e478fd2bde8d6472536d87f42a55dcbb1d9ad5b8785f666bb07841503
41d97e797d893e339dcff87180eef3be39d54eb3ec2f666ced27db404aba50d1
Both payments are on their chains and locked to the same secret hash 4e371a89d7a04c3a1d9128571cf1155cc96eb4d5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 9646da9e5238bd4d98475e0f03d9e7637fe933bfe50d899400780d6203153e5a
- TakerPaymentReceived: 41d97e797d893e339dcff87180eef3be39d54eb3ec2f666ced27db404aba50d1
- TakerPaymentSpent: 5fdbc16e3e866df27e5f23251eb5acb1118b49a1e7ccca0041040feee075a546
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.