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.
fae4058d7bdb4718389cb4c7958cb1b4ca46a00072a5db89bc1dda588f344415
Both payments are on their chains and locked to the same secret hash 4ba735d7d4d26a47a379b09fceb917749fa153f2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fae4058d7bdb4718389cb4c7958cb1b4ca46a00072a5db89bc1dda588f344415
- MakerPaymentSpent: 48ac7ccacd3e5612bb29f2911175fe77c3055f23c766751c3562df7c123f6c1c
848e876313b1376e75fc7ff0585558ed96faa50176772dd428e3e52311e11263
Both payments are on their chains and locked to the same secret hash 4ba735d7d4d26a47a379b09fceb917749fa153f2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7a6166d4001580b82d213b00625a456188e6bfe8262cb89b0bb9dd8db1623428
- TakerPaymentSent · TakerPaymentReceived: 848e876313b1376e75fc7ff0585558ed96faa50176772dd428e3e52311e11263
- TakerPaymentSpent: c5516a3b12362126e9546389b306831d3ccfa7cda67b2a532e4a24befc7a6659
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.