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.
4f4bde914940769fda8e9698bb177493f5323d2c05ba1bafd68132ea84a6cc3c
Both payments are on their chains and locked to the same secret hash 38baf196176c28fc853651c6de52240dbaaa4a91, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4f4bde914940769fda8e9698bb177493f5323d2c05ba1bafd68132ea84a6cc3c
- MakerPaymentSpent: 93257cdf54badfa3acf6d72bc60ce4d24154f21ed5316b402ba2e88572237d97
5cfaf32c33583bf5666745492842ad450be28860841609f6c7346d233e734aba
Both payments are on their chains and locked to the same secret hash 38baf196176c28fc853651c6de52240dbaaa4a91, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b35bee1aca2e37478ff1ab66686825cb3fa35debe80aa1e08ca52fbca79eec75
- TakerPaymentSent · TakerPaymentReceived: 5cfaf32c33583bf5666745492842ad450be28860841609f6c7346d233e734aba
- TakerPaymentSpent: 5e3fdae4144b52339f2c0889a9d3bd55e07c32c9895e924cf5378ed567f8d1a5
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.