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.
71a2ebcc0a2be15f7563cd7d2e859aa0c53509a2ecad4c08a5b48b2dce5bb509
Both payments are on their chains and locked to the same secret hash 8a45bf81384e7c86c1048543364969cb86ba9285, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 71a2ebcc0a2be15f7563cd7d2e859aa0c53509a2ecad4c08a5b48b2dce5bb509
- MakerPaymentSpent: 2dde559a1ac0ce31a86ea0b2fd3df6f4447673cfe62018e88458bb04ce320dfe
c33e75de7dd7c581bf8e8339f8e33fa0083aa1dc40789a1b06d5af30918c5123
Both payments are on their chains and locked to the same secret hash 8a45bf81384e7c86c1048543364969cb86ba9285, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 7e67474a391258f9d4c88e55c1e5744858e9c74c0111d52b7dc9316fd3718c76
- TakerPaymentReceived · TakerPaymentSent: c33e75de7dd7c581bf8e8339f8e33fa0083aa1dc40789a1b06d5af30918c5123
- TakerPaymentSpent: 9a29e36bff3e439257e975838b491a9947d47cb18fe734d2ba09a422975b29a2
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.