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.
6d1875e4606552c00e60d4d41787bf367c56d9196416da4970e78358774d0bf6
Both payments are on their chains and locked to the same secret hash 416078976257eab1e54d55f00e2ec18232fd7353, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6d1875e4606552c00e60d4d41787bf367c56d9196416da4970e78358774d0bf6
- MakerPaymentSpent: 59bf00990c98e4fb24e04867116c79a0d4be0570ab1b9674cb258c01b1d1163a
3852b74b30dfda398b9ad3194d2c3f90a8a2295bef578559083d3717022efb39
Both payments are on their chains and locked to the same secret hash 416078976257eab1e54d55f00e2ec18232fd7353, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cbac0519fe9feb8c19945f729ba192bd4e0c230f0c215c34eaffbfb2d27a9cef
- TakerPaymentSent · TakerPaymentReceived: 3852b74b30dfda398b9ad3194d2c3f90a8a2295bef578559083d3717022efb39
- TakerPaymentSpent: 8d7aae7ec7028c14e78ade5531c97773282caa9cd9e16dc3b571ad1c6bf04372
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.