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.
c549f05e10d2e4ff977973ade64fdd0eed59bf562b44030cf63729d9ec69bd94
Both payments are on their chains and locked to the same secret hash 49afd46d65e24d01caea09abf6ec18d10f7d7584, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c549f05e10d2e4ff977973ade64fdd0eed59bf562b44030cf63729d9ec69bd94
- MakerPaymentSpent: 7837207678e297f6970db3a2a8e3787479dfabcefd15dfed5ce9b91c4953e9f1
79382d3b7322dba0541be946ae2dff057fd84cac878319952f7bc08acaa81ff5
Both payments are on their chains and locked to the same secret hash 49afd46d65e24d01caea09abf6ec18d10f7d7584, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f531779439ed6f5679ca461c502492b7f7b1a99845909cb4d9add42b697bd5c7
- TakerPaymentSent · TakerPaymentReceived: 79382d3b7322dba0541be946ae2dff057fd84cac878319952f7bc08acaa81ff5
- TakerPaymentSpent: e9b64a1b3e083f062c2442b026c2d7e61fc967a04b507f0457153fb6ee54637f
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.