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.
4438d419eec3cd17600da27c3d610c803b7f4f97a56cb25f8c687fa6da51c5cc
Both payments are on their chains and locked to the same secret hash 96927c914b28ab86dac7c1075d1e64f9c2b1f156, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 4438d419eec3cd17600da27c3d610c803b7f4f97a56cb25f8c687fa6da51c5cc
- MakerPaymentSpent: 983d9b98b910232b79322f7743043255f3ec77a8c1766be89e339e3b1bf997c2
cedfa37b708e9f2ccabc59fc91e3d9a194db4ccf764fe14cffc370948901f11e
Both payments are on their chains and locked to the same secret hash 96927c914b28ab86dac7c1075d1e64f9c2b1f156, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f9932009cf3f9aa4b2e86e96b47c41dacba025c40554712ea554c7ee85149df6
- TakerPaymentSent · TakerPaymentReceived: cedfa37b708e9f2ccabc59fc91e3d9a194db4ccf764fe14cffc370948901f11e
- TakerPaymentSpent: 4bb842ef91aa6cab9d1029aa399ac7fea41532e4e9128f5e3f2422cdd078dc69
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.