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.
3eeee708405f9e4e5bde91afaef2e2f4f8e1aba85b717915b81618b9cb534035
Both payments are on their chains and locked to the same secret hash b83d96eb6be1a205811fe6407f4e5d4aae24d570, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3eeee708405f9e4e5bde91afaef2e2f4f8e1aba85b717915b81618b9cb534035
- MakerPaymentSpent: 93a320b7c8d8ce46cba9025a365f373e2e0254936e760975a3cd754b9b54fd60
350bb2d1582ae0b470698479e4db8a702a7f0d892df4456a99fdddcd5a276c5f
Both payments are on their chains and locked to the same secret hash b83d96eb6be1a205811fe6407f4e5d4aae24d570, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 834db25c0eb0458ca6287885aed8bc478e53bfe6cc6a7deca5547469460fe2b3
- TakerPaymentSent · TakerPaymentReceived: 350bb2d1582ae0b470698479e4db8a702a7f0d892df4456a99fdddcd5a276c5f
- TakerPaymentSpent: 5b2c884b04eee37cf926ba321ce3cd5db8d37b171308bc570297c34c71bc1618
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.