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.
2e1ff1573d5cc5591e83f8159df7a5a632f354f245181c7ee979c9b977a23c8c
Both payments are on their chains and locked to the same secret hash ac725ca6340e6ea853d0461e0db2bc0795e731c8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2e1ff1573d5cc5591e83f8159df7a5a632f354f245181c7ee979c9b977a23c8c
- MakerPaymentSpent: 925464c4a20b14daf2bb78c19f89e1a40cd81d20f249e93bc04624e05591d9e4
7dfd3af42b8df385d1553e8a818be1d7c2ca04ec743492ea9c911adeabb48053
Both payments are on their chains and locked to the same secret hash ac725ca6340e6ea853d0461e0db2bc0795e731c8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 29c2e8792beb180b53ff87573df71689821ab16a2e78f8eb85c6c2aaf1c7aafd
- TakerPaymentSent · TakerPaymentReceived: 7dfd3af42b8df385d1553e8a818be1d7c2ca04ec743492ea9c911adeabb48053
- TakerPaymentSpent: fefcec85ebd88f2ddd9468c90e8913d2f020cc38b344891dc87d11720e4a5e43
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.