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.
11bb66a6b4665df71052dafba5a6d04d035b385f47fb314835cf90a313486a82
Both payments are on their chains and locked to the same secret hash 1ab835e0bc8e1a6f159049c99b05752b787121b9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 11bb66a6b4665df71052dafba5a6d04d035b385f47fb314835cf90a313486a82
- MakerPaymentSpent: a82618904f7676bf82c7c8151ad81500f117ff1d5034d33275189c950167274b
554f695acfad464a685f2bde8f836dc475e7245f0f6a3d294900084819061ceb
Both payments are on their chains and locked to the same secret hash 1ab835e0bc8e1a6f159049c99b05752b787121b9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f8c1ccb924048ebb89f962cac74d0eccf213d8e51e75f3c7452bb519c49ce750
- TakerPaymentSent · TakerPaymentReceived: 554f695acfad464a685f2bde8f836dc475e7245f0f6a3d294900084819061ceb
- TakerPaymentSpent: 4a2ffa29b974caa9fa7d38058aab83aec6d82d73316a7833749c3c76bfda69b4
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.