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.
b0af20e0b8a51cfc60337f258461d27c148f517c148444eedf44f791d70afda0
Both payments are on their chains and locked to the same secret hash e8634d7be15a1a9daf5d3f45a79d10897c0831bf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b0af20e0b8a51cfc60337f258461d27c148f517c148444eedf44f791d70afda0
- MakerPaymentSpent: ae2615981837120dfdf681873d50f75c4bc24766dccc988bc478019658d6e7df
fc0783dc6841ff7480ca7320899210d712c72fdd777d9de48714737b3d81ef20
Both payments are on their chains and locked to the same secret hash e8634d7be15a1a9daf5d3f45a79d10897c0831bf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fc8ea8db95ae35610e94505b09b41d14a92dd3ab8aedc1e676b56bc1096f1e44
- TakerPaymentSent · TakerPaymentReceived: fc0783dc6841ff7480ca7320899210d712c72fdd777d9de48714737b3d81ef20
- TakerPaymentSpent: dc37c066d1ace8f708f2551d1c17648942d97eccf972442720c61d8289c87f9f
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.