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.
cb6bd3cd8813173ef0272f98eb06a55b84b5ff53a844c14317810a80609da836
Both payments are on their chains and locked to the same secret hash b6bdee735197f9d0c28e3c53a1d17dd3a0d0149d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cb6bd3cd8813173ef0272f98eb06a55b84b5ff53a844c14317810a80609da836
- MakerPaymentSpent: 478035e99d99f334625594c347443168be54efbc7ca793fc2ae353910db637e9
0a628bc8cc06956ba01598cce20c162003f0d00ea8263038ebbfac5ed3119fd2
Both payments are on their chains and locked to the same secret hash b6bdee735197f9d0c28e3c53a1d17dd3a0d0149d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c8d31c437dd64c5e5d346222898750ec478ee60e66b275dc69f30b5833cb5d99
- TakerPaymentSent · TakerPaymentReceived: 0a628bc8cc06956ba01598cce20c162003f0d00ea8263038ebbfac5ed3119fd2
- TakerPaymentSpent: 998ff4f5e390fb3d5e07c127edeb97a6dd51b950e5d106cae1dc74d8eae713e0
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.