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.
ff6c3035ea363cccd210d009fea2936678f3170655d27c053f89e708341a8ad7
Both payments are on their chains and locked to the same secret hash c1efd15d4d9d451d480b2263b52e831833711ea2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ff6c3035ea363cccd210d009fea2936678f3170655d27c053f89e708341a8ad7
- MakerPaymentSpent: f7bec0bea93144f4324dbffb6235108ce044061766a7b6cef85989ca6d7f4436
657e12c668a108cf8b61e401871ad403154b0d853974263481248236a0710f75
Both payments are on their chains and locked to the same secret hash c1efd15d4d9d451d480b2263b52e831833711ea2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c0141db0311346b84c0f8005eedb4fca6f2e6fa0d5a35893a92e1bae8838dda3
- TakerPaymentSent · TakerPaymentReceived: 657e12c668a108cf8b61e401871ad403154b0d853974263481248236a0710f75
- TakerPaymentSpent: 2d31c97e6eca93de93cdc8057934cccfefb6fa711900d91909215406dc086b75
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.