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.
93349ac05e9392e5ba6a0a32556473ff5e9ffe2179f39d32bfffcac0c1838c4d
Both payments are on their chains and locked to the same secret hash 3e17eaa043244956a0ba6092a2c9bb35f706b3e1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 93349ac05e9392e5ba6a0a32556473ff5e9ffe2179f39d32bfffcac0c1838c4d
- MakerPaymentSpent: 0322a38044785a0f67e62aa71d7f946c310148743941c1649a6ce783bf88c260
26dc6f2dba84607426dbaf57fba0882cf887c0296cd0970c2e4d408dcdb879ac
Both payments are on their chains and locked to the same secret hash 3e17eaa043244956a0ba6092a2c9bb35f706b3e1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 31ea3a7ee5e80036b7929f54b2eb90a56846de36add1b0daea6a84ecf96078eb
- TakerPaymentSent · TakerPaymentReceived: 26dc6f2dba84607426dbaf57fba0882cf887c0296cd0970c2e4d408dcdb879ac
- TakerPaymentSpent: bbb9b2299bb8142c451c014271f586e8cb40da14da28868377fe3635bf3751c9
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.