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.
9b91247a7174d024309bb1a7741f42270d25c6459f95ee3831282a97524008b0
Both payments are on their chains and locked to the same secret hash c26d2f9f991cc6d748c9763f355cc32c11c6aa4f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9b91247a7174d024309bb1a7741f42270d25c6459f95ee3831282a97524008b0
- MakerPaymentSpent: 5fd9b541e1279775940cb170115606edecef4ef432faccdbe45aa5ddebac607c
e79c51649fa3bccc70c202949ad4ae1085bf843c761aa44229836cec001d1552
Both payments are on their chains and locked to the same secret hash c26d2f9f991cc6d748c9763f355cc32c11c6aa4f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5b48c0b6e00f2cd4a7e4b323b71e67685c5d8f779fa5e463ddb3ed8eef603a68
- TakerPaymentSent · TakerPaymentReceived: e79c51649fa3bccc70c202949ad4ae1085bf843c761aa44229836cec001d1552
- TakerPaymentSpent: 8f6576999aca8159b4428e0427dd315fddc46c69039cfaaf7ba40c4785f94123
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.