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.
ede589eb139bd5e468da6bb7eed3aaa27bc85532ad1eb8bc514c674f998d12a7
Both payments are on their chains and locked to the same secret hash 60903ec61e2c2c2cb973b3fc8330098da7985ffb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ede589eb139bd5e468da6bb7eed3aaa27bc85532ad1eb8bc514c674f998d12a7
- MakerPaymentSpent: aff36af5be54986f41ec4eff4eca1a158ffd79379e36506545a9d303d768d97b
879c0b7d49f187f9183fd98bacfdf1b434a4b902c85dbd9d44385cf7d4d6e780
Both payments are on their chains and locked to the same secret hash 60903ec61e2c2c2cb973b3fc8330098da7985ffb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5a82e965d8c1a6cae1db953cf58983ffe12677a9435da881412a58f12e8a293f
- TakerPaymentSent · TakerPaymentReceived: 879c0b7d49f187f9183fd98bacfdf1b434a4b902c85dbd9d44385cf7d4d6e780
- TakerPaymentSpent: 481d60de96fc8495a3b4c3f92f557996f7110fbfd2c155944d3398125ce6c1d8
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.