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.
f62a34173e8e8b714e120f1a0a96f28876cf32d5fd120bd2f0129e66c3d05038
Both payments are on their chains and locked to the same secret hash 8cc81c0ebdbbb37fa3ea25add7109daa800e4700, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f62a34173e8e8b714e120f1a0a96f28876cf32d5fd120bd2f0129e66c3d05038
- MakerPaymentSpent: cd2a3f35aec4bc1e668aa220322d482404c98febe2463c784dc5604849a4ead0
f72a58d50d2e74be68ee82fef01884d386223d5b7f1fb444a9f11828abad143e
Both payments are on their chains and locked to the same secret hash 8cc81c0ebdbbb37fa3ea25add7109daa800e4700, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ed14b8b76312123213d77e5442322d6472314ccbd86c095f0d994a8b18eb4eff
- TakerPaymentSent · TakerPaymentReceived: f72a58d50d2e74be68ee82fef01884d386223d5b7f1fb444a9f11828abad143e
- TakerPaymentSpent: ebfe3b0a6d775a076785784ece58fe00173daf8fd2ef3edad86e909f82efc672
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.