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.
09b1199a119264cefe05ace8caad00146e539aa4d695dfaec14470a1aecb5fa6
Both payments are on their chains and locked to the same secret hash f6358febcd741f6f288a43c63a7995b97cd93db5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 09b1199a119264cefe05ace8caad00146e539aa4d695dfaec14470a1aecb5fa6
- MakerPaymentSpent: c9b3f5bd206dfc49991ae278ad02c0c50bf50dc930df1e03be78ef48d9b369c4
af4a49068bffaab24b3de0b4bf9b3d3720ab78b2eadeddb86e1eaca0b46574bd
Both payments are on their chains and locked to the same secret hash f6358febcd741f6f288a43c63a7995b97cd93db5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 69ccf26c2038b1aa796c4d7bf89347acc6090b3004ab93b093729670f7766522
- TakerPaymentSent · TakerPaymentReceived: af4a49068bffaab24b3de0b4bf9b3d3720ab78b2eadeddb86e1eaca0b46574bd
- TakerPaymentSpent: f149c1797dcd21939f988d4c24b1383a5595cdc4f17672ed58cdeeffa50e5bf1
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.