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.
749b45a27ec19651b31f0a919a40f13d90ab55a2d5f7b379f6324189fb9b9453
Both payments are on their chains and locked to the same secret hash 99a1d406e1dd09f8de020e57daf367476fbfec01, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 749b45a27ec19651b31f0a919a40f13d90ab55a2d5f7b379f6324189fb9b9453
- MakerPaymentSpent: ca107cf01e39d407bd08873004dfff40042b5c02568c1347fac57f49e02bd738
0a470ee92e7a3a1068eaac76891369fdd40a03393f4b89d630d0ea5234511f26
Both payments are on their chains and locked to the same secret hash 99a1d406e1dd09f8de020e57daf367476fbfec01, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: db180ce28bc2d966a90440092aa30e5485dd34ec67b6ab8d882efdbcac71bcd4
- TakerPaymentSent · TakerPaymentReceived: 0a470ee92e7a3a1068eaac76891369fdd40a03393f4b89d630d0ea5234511f26
- TakerPaymentSpent: f59b573b876fdd7950940dbca27bd69f00d9c068aa5c4cd30e4e330ee6cc986d
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.