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.
1253dbf4d8dd186c2d311be40ceb00e7d1025f4be7ee11c26e88b6843dae9035
Both payments are on their chains and locked to the same secret hash b40273fa2552a6ea9ba8feecf875613c912e3c6d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1253dbf4d8dd186c2d311be40ceb00e7d1025f4be7ee11c26e88b6843dae9035
- MakerPaymentSpent: bb2f3fa172eb9aecaac528c93bc55d466f55934d38f6bb0f8e5c21ff3e98ba0c
51bfdfdea07f35d0a8365678fdca7bd5c26010e026ac08057b20606b4baaa645
Both payments are on their chains and locked to the same secret hash b40273fa2552a6ea9ba8feecf875613c912e3c6d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 142ab6c36f91b0881a5378590c61dc2623669d10d7b006edc025ea5bbf98be65
- TakerPaymentSent · TakerPaymentReceived: 51bfdfdea07f35d0a8365678fdca7bd5c26010e026ac08057b20606b4baaa645
- TakerPaymentSpent: 6e4ae585e39dfee29bed68cd429a0e418c29a37c39e2ed0ef569bb160e9f9de2
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.