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.
46b6f7178e7e53ea82568aceae63c78526efe87bcdd7203d1f7dc9089ede7505
Both payments are on their chains and locked to the same secret hash 00842529f0f8935717e2aa81bf67cfddc6183e2d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 46b6f7178e7e53ea82568aceae63c78526efe87bcdd7203d1f7dc9089ede7505
- MakerPaymentSpent: eb864f71d5a21b10a1dae432f186a3a6c6352513cacffe67a6ab165e3f34a1a6
a0394502143082bc260c1053dec5c9aeec1693af265423a86e7e360bd10d8e5c
Both payments are on their chains and locked to the same secret hash 00842529f0f8935717e2aa81bf67cfddc6183e2d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: abb914544b30ee80a8286db4e11282e345628a62f6d1b86fbc63030ef7e9fd94
- TakerPaymentSent · TakerPaymentReceived: a0394502143082bc260c1053dec5c9aeec1693af265423a86e7e360bd10d8e5c
- TakerPaymentSpent: faa1136412c031ce867a8afc1dbaec22db87405552a15f9da4ba72cece16d9e2
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.