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.
dbeeefa598e447d24153d75d3807aa24fc8d8ffb1b378fca203760ba457b94fb
Both payments are on their chains and locked to the same secret hash 2351a1934ac38e9817656819007f578c077e9160, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dbeeefa598e447d24153d75d3807aa24fc8d8ffb1b378fca203760ba457b94fb
- MakerPaymentSpent: 8b0ea869d2b0c4f5f1c588aa8dd86724d776d366f9525aa5b02fc36ec764aa0f
41f5abf333697772e1fad6499bbda708e06b99a46c16dfc07aa75be534550b78
Both payments are on their chains and locked to the same secret hash 2351a1934ac38e9817656819007f578c077e9160, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bcf88cb54b1a7240872986ca00575fd67efecdda34b22fbd95728aa8b160391d
- TakerPaymentSent · TakerPaymentReceived: 41f5abf333697772e1fad6499bbda708e06b99a46c16dfc07aa75be534550b78
- TakerPaymentSpent: 28f97ea9410e4872a6ab1c22b8647c0990dd652e385b15246a788801abdf5fe3
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.