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.
255d7f1bacf04c7e42a06032fcb09f149f6238a6bf811377229c057cae7d60c6
Both payments are on their chains and locked to the same secret hash 4c12038893469fcca5280e75adb038b5dca64187, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 255d7f1bacf04c7e42a06032fcb09f149f6238a6bf811377229c057cae7d60c6
- MakerPaymentSpent: c2e6d56ced0b19e4948c05febb3dfb2baff779deb47606d64b7b739b4ab8e28f
408104288a95121ce311cd17baacc057a3f254e0a56e1129184ea43598273ee0
Both payments are on their chains and locked to the same secret hash 4c12038893469fcca5280e75adb038b5dca64187, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 86183b511d3a508fb25e034dc1d94e05453492c0be61ba2ea7187765ffc430b9
- TakerPaymentSent · TakerPaymentReceived: 408104288a95121ce311cd17baacc057a3f254e0a56e1129184ea43598273ee0
- TakerPaymentSpent: da92c9350c88ad6ad0e0430b319ea6ba5cef9fd027192d675c687e994c226a9e
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.