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.
78608522297dcd99135aa1083a252681895ee125f2bc6f917e63aac100e3cde7
Both payments are on their chains and locked to the same secret hash 6692ae70986c76986c78c994ec80ef90e0504355, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 78608522297dcd99135aa1083a252681895ee125f2bc6f917e63aac100e3cde7
- MakerPaymentSpent: db5cefa2801b2a0c56b08386bd8f6036f869e74885cfd2acffd2707d41130bfb
79d072664f28df965a597247f76c9c440c7f8ddcce42d0fd54a2b41a6b91aa45
Both payments are on their chains and locked to the same secret hash 6692ae70986c76986c78c994ec80ef90e0504355, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b2b5e4f58b4cb87a36074a3842adfd4816b0607f70a0ee5f2b0806fcf97d7f07
- TakerPaymentSent · TakerPaymentReceived: 79d072664f28df965a597247f76c9c440c7f8ddcce42d0fd54a2b41a6b91aa45
- TakerPaymentSpent: b3f209b71467d2a3316a26489170e9d77889ea5134cbb086f3d0e50188a8e090
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.