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.
88d590cec755ddbf0d0369f2dad1484bd45455bd931d9d3bc7398101e3e1fef1
Both payments are on their chains and locked to the same secret hash 79e35b6b9e65969b3c0c58f927827182783262b6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 88d590cec755ddbf0d0369f2dad1484bd45455bd931d9d3bc7398101e3e1fef1
- MakerPaymentSpent: b542728f59e1f1d9139f0449d747e2986a19221382599c80fb700c1e0f5cc99e
7721ae2c63f2cb594d6eba2aaacbc25316197b1bc319a90e432fe1f8f6a1a7cc
Both payments are on their chains and locked to the same secret hash 79e35b6b9e65969b3c0c58f927827182783262b6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 811305ee048c04034dd349cf0fed3d0d6e29cce5f85b74e09819f30298275f9a
- TakerPaymentSent · TakerPaymentReceived: 7721ae2c63f2cb594d6eba2aaacbc25316197b1bc319a90e432fe1f8f6a1a7cc
- TakerPaymentSpent: c941cbd57e07c3589c5d99fffbcf4fe2b3034a8348be153eeb81e3f11a697bd8
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.