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.
4c2ddb300e7368bc65586e9eea194a0a88289d9a1d9026a7f6b93125e6410479
Both payments are on their chains and locked to the same secret hash 6f6c6c4d72a66d52142f30e1eb69f6b335f9cce7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 4c2ddb300e7368bc65586e9eea194a0a88289d9a1d9026a7f6b93125e6410479
- MakerPaymentSpent: 546f9e5ccef2ad8d6faea27ae9430f74b1cae2e71281c63ec556efc16227a9aa
50ddbb615db9f7053282fca32a5486b02b3329fb80aa99a47db1717746989e15
Both payments are on their chains and locked to the same secret hash 6f6c6c4d72a66d52142f30e1eb69f6b335f9cce7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5a5a25b78f1140db5a1b1bae72416c5ecc6d7c6b6108582d6c5e9403e26dcd17
- TakerPaymentSent · TakerPaymentReceived: 50ddbb615db9f7053282fca32a5486b02b3329fb80aa99a47db1717746989e15
- TakerPaymentSpent: 2e15abea879d4e41be5b10913f4020b193a5481e88cd527d6629b04c002d391f
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.