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.
9620e86e331bc6815018a219e6c7b9e51e3447930434fdbce916eacf85dab502
Both payments are on their chains and locked to the same secret hash 6cfd2e6fdf750ece859ce2afabe428f4f7eb5518, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9620e86e331bc6815018a219e6c7b9e51e3447930434fdbce916eacf85dab502
- MakerPaymentSpent: 51dcacebd2221ed77d570b49ffcea509c318b3eb4ede7c7ef0aacee3a86a1d80
1108c3e142d6575ec73a022d69459087c27afa19fbe4f3fee90cba951d489c28
Both payments are on their chains and locked to the same secret hash 6cfd2e6fdf750ece859ce2afabe428f4f7eb5518, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 23483406022e714b7d46b9f90a79cac27f7a9862bdee31de5d5ad5f199ea6e85
- TakerPaymentSent · TakerPaymentReceived: 1108c3e142d6575ec73a022d69459087c27afa19fbe4f3fee90cba951d489c28
- TakerPaymentSpent: 7f413820f643a4693d412eb5267eb895de92f1bae78bb963cdbf04e90d55a0b3
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.