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.
aaee3ff1b4290a9a7fe4f8119d0e845a28552845bdb285c001a0fcfdbb5f6ae4
Both payments are on their chains and locked to the same secret hash e4d017f33d6cc76f9014b32e008e91b152d305d1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: aaee3ff1b4290a9a7fe4f8119d0e845a28552845bdb285c001a0fcfdbb5f6ae4
- MakerPaymentSpent: 580a6b635e4e31d57a6dbcdb0f8e805cd4ab5c64b4374936961fb562b9395fab
f75e8e957852523395d2ce0d163bdabdd8e9b8b0c983328de64161f4a283a656
Both payments are on their chains and locked to the same secret hash e4d017f33d6cc76f9014b32e008e91b152d305d1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fc791c4279932294ac127e736b1c567996321f72f2c784639368efda7a8d09fe
- TakerPaymentSent · TakerPaymentReceived: f75e8e957852523395d2ce0d163bdabdd8e9b8b0c983328de64161f4a283a656
- TakerPaymentSpent: d602a728b99bc43a4e438d991f1c26b4a49a3482974c396ea969cd4af8aa3f83
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.