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.
83419a36ebd40973d012c284e553062fb78f141b7103a08737d8cc7c9e1bc6bc
Both payments are on their chains and locked to the same secret hash d272c1a985f597fa292c53a0776de211747527a0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 83419a36ebd40973d012c284e553062fb78f141b7103a08737d8cc7c9e1bc6bc
- MakerPaymentSpent: dd77a94facda3ac5ecdd2c4ea6374818959001d92e4e7e4cf736849fbc4b81da
506291a59b467dc5fa8dc87ba53ac591eea175c2eb282267f326e165a708aeeb
Both payments are on their chains and locked to the same secret hash d272c1a985f597fa292c53a0776de211747527a0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f59d972cb64a8e236645336e4b6d9666739782c0d4728a108156b93138ee49f6
- TakerPaymentSent · TakerPaymentReceived: 506291a59b467dc5fa8dc87ba53ac591eea175c2eb282267f326e165a708aeeb
- TakerPaymentSpent: 3a2d6ea123c5bcb784acc6e7003cc1e3474b5db72c7cdcd0a3773a451e80d6db
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.