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.
6d797aa6949d2cbf6974d3cefe483b5e4916836a83cddebf1876f47dccda176f
Both payments are on their chains and locked to the same secret hash 4f8468274ad297db093ef96f5db48774ac542d6d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6d797aa6949d2cbf6974d3cefe483b5e4916836a83cddebf1876f47dccda176f
- MakerPaymentSpent: a921122aaa48b70dd0be9a1aa551fdfa7ffe38e7679bb4d66dd04ae0acbfb070
ed85ab6c289bc15d51ed7c31acb134ffc230861e03aec6f8572cdb1106a3b224
Both payments are on their chains and locked to the same secret hash 4f8468274ad297db093ef96f5db48774ac542d6d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3d2d684105ffd42fe742e57244548d4aac2f4971f2cea3080ad1b9cbe7730d03
- TakerPaymentReceived · TakerPaymentSent: ed85ab6c289bc15d51ed7c31acb134ffc230861e03aec6f8572cdb1106a3b224
- TakerPaymentSpent: 3d1c9453b69e241779a277256ca7d4b6396df9251d0f6688db5e797d9a402ff4
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.