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.
24baa72378f729f1ed3e834b92ea04362312bfc31e1d16e993619b7b6c8a3679
Both payments are on their chains and locked to the same secret hash f1c2d1b4b126c293e8de9c56bcd0a2c597656af9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 24baa72378f729f1ed3e834b92ea04362312bfc31e1d16e993619b7b6c8a3679
- MakerPaymentSpent: 77ba4e0e938af91cf29368f76b06856242a5bdd682c235981a199bd6605b7672
89c000e9d04cd48d8c5f64aeac0990a043b521082f60d9bfedc84590d0a93361
Both payments are on their chains and locked to the same secret hash f1c2d1b4b126c293e8de9c56bcd0a2c597656af9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5f8ca4e62a05755fbf34f0e08070e30739fa88e58213a3e02a94d470e5394590
- TakerPaymentSent · TakerPaymentReceived: 89c000e9d04cd48d8c5f64aeac0990a043b521082f60d9bfedc84590d0a93361
- TakerPaymentSpent: 93d661720d9ed7e9fc2d23c31cdc318492cec9eac72e06b5e04815bc43804fee
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.