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.
96745399ce08c9a2f97ada8b066b149311c7356f00651ecb841ab5dde9f16dee
Both payments are on their chains and locked to the same secret hash dc11e570f9026256966b21066a85c58f9f3665fe, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 96745399ce08c9a2f97ada8b066b149311c7356f00651ecb841ab5dde9f16dee
- MakerPaymentSpent: a47894db6ba00800f93f893f3d8072cc1bc0cafda00b33913953fab488f6aa99
4456254c7e24dc8cccbc09965ed87ac351fbbaa91b1ed10382ea51d54aefd573
Both payments are on their chains and locked to the same secret hash dc11e570f9026256966b21066a85c58f9f3665fe, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aa9ff41c0e23ba51821d863d7c827821478c6f504a5ba2c3006083df0e4bbf57
- TakerPaymentSent · TakerPaymentReceived: 4456254c7e24dc8cccbc09965ed87ac351fbbaa91b1ed10382ea51d54aefd573
- TakerPaymentSpent: 9d398f6dbbfcbd7af5bd1a8d08f0623589a331c6156c520d05428d0d72216fdc
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.