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.
19e6610ac8c70835ebba32a4163861d56a917920af213b919321b876454e5c2a
Both payments are on their chains and locked to the same secret hash cc140dfa1ddb6d53398d524e4fb85a914c08d1dc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 19e6610ac8c70835ebba32a4163861d56a917920af213b919321b876454e5c2a
- MakerPaymentSpent: 6f16563b979df29eb9d09ee58d187d01dc5bc5bcd144fe7030f8ce55f3575e7c
10f2e1efeea6ce6da755ac87636eef0dde5b618d5cf912ccf7ce5b9b9dcf71a0
Both payments are on their chains and locked to the same secret hash cc140dfa1ddb6d53398d524e4fb85a914c08d1dc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a6966f2d382b6a347ff1fe84f1ea6ec69b81eb8bde20c73ef143b3fceae0f0e7
- TakerPaymentSent · TakerPaymentReceived: 10f2e1efeea6ce6da755ac87636eef0dde5b618d5cf912ccf7ce5b9b9dcf71a0
- TakerPaymentSpent: a57c43aad5533a9c8d97579233d191b5b426a848328d354e897162b8d540de50
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.