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.
6757f961244903bf2d7159bc505b5539615dbdd24814be1679a20a8911ad7869
Both payments are on their chains and locked to the same secret hash 3921ca3410bd0038a5895240ab23addad2dd0363, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6757f961244903bf2d7159bc505b5539615dbdd24814be1679a20a8911ad7869
- MakerPaymentSpent: 06aff5dca51c5d1c84e26a321590492b8388e8b6f7efdbed1abda4916e195f24
9cc8f9527ec09ae00c20f0e7b0ed5c29cf93cd547965d2e87ed4f0c9d5334f23
Both payments are on their chains and locked to the same secret hash 3921ca3410bd0038a5895240ab23addad2dd0363, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 25c55c2d9d44fd5e905ef4acc478f281fbb91de4fc71a9c19477ca2691734276
- TakerPaymentSent · TakerPaymentReceived: 9cc8f9527ec09ae00c20f0e7b0ed5c29cf93cd547965d2e87ed4f0c9d5334f23
- TakerPaymentSpent: dead15e08b3cd0b2a0abc9b3ed7b70af10042fb8ad289137ea1fcfc80d7d3736
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.