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.
dd43edfb6cc11a9c6a50a24ed5636f3ceed36051709a379380e6e98617bb14ce
Both payments are on their chains and locked to the same secret hash 8ff9b57f2fd438a7b1c4ead615d57df4f5a600a6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dd43edfb6cc11a9c6a50a24ed5636f3ceed36051709a379380e6e98617bb14ce
- MakerPaymentSpent: b9fd96760b2a2b498e47bb3fbb712a454acf989e00f88b8dd166fb57a4ded9b6
4fbe32d18aafaec1bedc8d65ecb911c5363b611c8416f19948c92cb55b7d5213
Both payments are on their chains and locked to the same secret hash 8ff9b57f2fd438a7b1c4ead615d57df4f5a600a6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c835fea34a5b52ff90f385a822d7f1e18685b8c72ef7a4b8bc93499534ba847e
- TakerPaymentSent · TakerPaymentReceived: 4fbe32d18aafaec1bedc8d65ecb911c5363b611c8416f19948c92cb55b7d5213
- TakerPaymentSpent: a1ec8d013d851cf597ff4e42fad20d740aa46928d3ec9b439bb59db13c19da17
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.