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.
a3cd76a1b8000389959284bb0b8b2049b58c7dd668f3f1975168722774a1a7cc
Both payments are on their chains and locked to the same secret hash f48187191752ac36eaf66367c612d04a068ef7ca, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a3cd76a1b8000389959284bb0b8b2049b58c7dd668f3f1975168722774a1a7cc
- MakerPaymentSpent: c85690dd8652b1b39d4f1f29afc3cc20bec1ea33c184592018d428b26f6a318d
80e758ff1076e4eecfc897870a44fa65dd31215a77580be02d98a2415050e29b
Both payments are on their chains and locked to the same secret hash f48187191752ac36eaf66367c612d04a068ef7ca, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6fa512c5ba9d85c408ddf79b1234c918ec5c1f1dbce84c4d5b585f866beb3c2f
- TakerPaymentSent · TakerPaymentReceived: 80e758ff1076e4eecfc897870a44fa65dd31215a77580be02d98a2415050e29b
- TakerPaymentSpent: 016b18f8047b1d36be8d118479fb9103129bb66016acb5da550a875b950593de
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.