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.
3ed40fe0101d8bf126ff6c7c9953292de5941981d60b13944179ff76aa982308
Both payments are on their chains and locked to the same secret hash c343c5a33de9c23877409754cc446bac329a3754, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3ed40fe0101d8bf126ff6c7c9953292de5941981d60b13944179ff76aa982308
- MakerPaymentSpent: 7cd08cfcddf330e4cc4d7ed32ff0a33c3c982760c35c50bea1f3b31fd142151e
b83e7670a480f84e12c83e5430d530532985febb3fd832ac8b6a1a648cb49ca6
Both payments are on their chains and locked to the same secret hash c343c5a33de9c23877409754cc446bac329a3754, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 6de72081c7b347138412c7eb4c55f2405101fa947a09dbd4350a9f153545ee94
- TakerPaymentReceived · TakerPaymentSent: b83e7670a480f84e12c83e5430d530532985febb3fd832ac8b6a1a648cb49ca6
- TakerPaymentSpent: 8830254cb1b67897091f101941eb969aabce4c1853eb629bc86f34df797fb216
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.