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.
e0647a1c794ac57e644d8bc56749445657069247fccad59d3b47e7456138a57d
Both payments are on their chains and locked to the same secret hash 0f2ae25eafa635e2e95be6e7047c69f67ee8d204, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e0647a1c794ac57e644d8bc56749445657069247fccad59d3b47e7456138a57d
- MakerPaymentSpent: 31cf0e0683fea391ce38a0512a99e006aaa9792c1915b3100394ff5f3971838c
ac642bbca027490d82e71ac44c12fafe147a445810544c965f162cfd23560dd9
Both payments are on their chains and locked to the same secret hash 0f2ae25eafa635e2e95be6e7047c69f67ee8d204, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 702cb29ceb08a80e070f780ee4305a7f6cbd81f1c15c880b28824589be4850d3
- TakerPaymentSent · TakerPaymentReceived: ac642bbca027490d82e71ac44c12fafe147a445810544c965f162cfd23560dd9
- TakerPaymentSpent: beba556dbe7e84f970d32da31a15c547feb84a83ee425a45ce9eb1afdb4fcd4d
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.