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.
244d7dc77663a3ec0abbe86861267d7b00462c454876d3379f0417f06d00afcf
Both payments are on their chains and locked to the same secret hash d130b886363ca558a0c80621b01b645fbdf586e3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 244d7dc77663a3ec0abbe86861267d7b00462c454876d3379f0417f06d00afcf
- MakerPaymentSpent: c50291885eeb2fa09309d0638e2c5d1196ac69251ed8a0400d354b81df48ce69
380172ed1ca493396f33c7902beae5bae1a5868d6563e1c706d637b0303ef7e2
Both payments are on their chains and locked to the same secret hash d130b886363ca558a0c80621b01b645fbdf586e3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 14a52046f141c98a7c3a39cda75b0a9682511567272ee57fe6cd23efc6244afa
- TakerPaymentSent · TakerPaymentReceived: 380172ed1ca493396f33c7902beae5bae1a5868d6563e1c706d637b0303ef7e2
- TakerPaymentSpent: 278d3688aa99204e229cf9ccddacf81843c5a1df695e65563cd518f0f4e931ef
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.