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.
c054013756e14058f4d999eec8fb21c9a405c0b6dda59a17a497bc458dad4bf2
Both payments are on their chains and locked to the same secret hash b03c39000ba41bd99722d9ae10fe9bb472aaaddc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c054013756e14058f4d999eec8fb21c9a405c0b6dda59a17a497bc458dad4bf2
- MakerPaymentSpent: d6164d5cf0ef80fc9adc303be4ea85b8cfb7e0664c3cc2a3bc956b18961c3d8d
943c58813a898da197f4da8a5e11fdf00fb6de40fc958c74f1cf523800728fe3
Both payments are on their chains and locked to the same secret hash b03c39000ba41bd99722d9ae10fe9bb472aaaddc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a695e88eb7000edb5bcaf135c4a5219b608912043b0747e5b3161f63fbe7df63
- TakerPaymentSent · TakerPaymentReceived: 943c58813a898da197f4da8a5e11fdf00fb6de40fc958c74f1cf523800728fe3
- TakerPaymentSpent: 34db3cf925e91d857727f1b485fef6f0fc437fbbc5693922156f06cce5061283
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.