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.
43d3c85c0179d095ab9db6b97c649a14cc5d7f67da85b7a3fa4a64fec14a4241
Both payments are on their chains and locked to the same secret hash fafe177988db963cd43dd79d922bf6d420310ca6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 43d3c85c0179d095ab9db6b97c649a14cc5d7f67da85b7a3fa4a64fec14a4241
- MakerPaymentSpent: 511263cee9f6faab5103d82b90a062eca8385036da4aa7eb19886458b689e362
4f5eff9856f7213340595e5d4e36f2e8c86719d88e2542ca3cdfe361abbc8475
Both payments are on their chains and locked to the same secret hash fafe177988db963cd43dd79d922bf6d420310ca6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2a9e68e8f227f4a7f28fec0d2b51c288dec54ce8455f99d3eb7b835455c7d489
- TakerPaymentSent · TakerPaymentReceived: 4f5eff9856f7213340595e5d4e36f2e8c86719d88e2542ca3cdfe361abbc8475
- TakerPaymentSpent: e042fc18b5fc653a7a6cd4b2347f5ab3f07f1607c1ef9f3e717ca00ca5d320bc
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.