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.
b29f744b720137449a58bf796ae57a8855f6bcfd1a53ddb3df6056068f65d7db
Both payments are on their chains and locked to the same secret hash c902ca05d8507c9d609c63174674adfe3039537d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b29f744b720137449a58bf796ae57a8855f6bcfd1a53ddb3df6056068f65d7db
- MakerPaymentSpent: 4cd19fc09f8a236a86fb4be389273ade1fb20b54889894e81f30700c52067064
59fab67e7c283df946692876535b54abd0656a0538ab865e5cdb0e277107dda1
Both payments are on their chains and locked to the same secret hash c902ca05d8507c9d609c63174674adfe3039537d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cd208f9ddad87d88cf592f0da12e25b83a174ef1fc41441cae40e295ec729724
- TakerPaymentSent · TakerPaymentReceived: 59fab67e7c283df946692876535b54abd0656a0538ab865e5cdb0e277107dda1
- TakerPaymentSpent: a1db64d6ffebed18450f704095bf0ccd379b93e4baee82b8ab3fbbd8ff5d3b3d
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.