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.
0f1a8bd8f6d8d7143fd77ff4a3d785896358d811947d6f5248e78030c34912b0
Both payments are on their chains and locked to the same secret hash 18adb5d4117f5d8001ce24f50c2473b727d97f9e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0f1a8bd8f6d8d7143fd77ff4a3d785896358d811947d6f5248e78030c34912b0
- MakerPaymentSpent: 0433197fd1276a210c1e14cca296dead4bc59a2e60961ad8c0372925fe136541
9d2d73cc7513d4c5a7ebc977d2e9b5c61b462765e8cecbcf142567453c7dffdf
Both payments are on their chains and locked to the same secret hash 18adb5d4117f5d8001ce24f50c2473b727d97f9e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 95ef12984a840eca70d540a4b23d00f47cb1fe03dffd9ec08747cb3673b9bcc7
- TakerPaymentSent · TakerPaymentReceived: 9d2d73cc7513d4c5a7ebc977d2e9b5c61b462765e8cecbcf142567453c7dffdf
- TakerPaymentSpent: 522d4d5f11dbd8ad133ff9af1f51d4cfca4a0cbad0b9fc697d5da8cc9e733119
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.