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.
2b98bf0cf6ad6c4b58e4e112811fac1ff62cdf5c7377577798156cdf55ee4780
Both payments are on their chains and locked to the same secret hash 388a13e8fe4e1c65de4eefe4d22ac5c58406918e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2b98bf0cf6ad6c4b58e4e112811fac1ff62cdf5c7377577798156cdf55ee4780
- MakerPaymentSpent: ef69244f26204420bc31c1cf9cf62c73b477e459af060a6ddad681af98e72c1c
a57b3a5be65f999de4abda497062b8e3a1ffe944e707c3fa40fd177cd94d9bcd
Both payments are on their chains and locked to the same secret hash 388a13e8fe4e1c65de4eefe4d22ac5c58406918e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 686d3fdc22943ae611d283a2f1a652af969ba7037ba530e9a17dd1067e15d569
- TakerPaymentSent · TakerPaymentReceived: a57b3a5be65f999de4abda497062b8e3a1ffe944e707c3fa40fd177cd94d9bcd
- TakerPaymentSpent: eb684c82c64a0046076c7ee4f53369775fdbe968ff3103dd92dff71fa0cfa307
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.