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.
70850310256fcbe283ac41c49297f74ce86a02f965ce072139cc6ae2b72b9076
Both payments are on their chains and locked to the same secret hash c95bf539cbaf2ecfd08a832b4cc0c9445994e134, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 70850310256fcbe283ac41c49297f74ce86a02f965ce072139cc6ae2b72b9076
- MakerPaymentSpent: 26313a850ce81303f235a90a0969f761f3774f9055a1bf02242c55bb5df366e3
5cd8ccd24eab76f771c69efb85b04a35af56dc92104b75160a9d9ef9cf22cd46
Both payments are on their chains and locked to the same secret hash c95bf539cbaf2ecfd08a832b4cc0c9445994e134, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b2e3d9636e18c0ddf44fe923fe529ae852bb57a4d315d251093f53d2b1f3ba32
- TakerPaymentSent · TakerPaymentReceived: 5cd8ccd24eab76f771c69efb85b04a35af56dc92104b75160a9d9ef9cf22cd46
- TakerPaymentSpent: c22ba84924f977045c44a571a365a5686b3b6ebb48a7517bce9c3f75bdea6322
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.