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.
63cebf7129b3d3abcedd86c20c5f1b6f30308a771ee4a27911f8b98a59754486
Both payments are on their chains and locked to the same secret hash 789872d4cc4be60582d3dc67cfe22c640378c45e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 63cebf7129b3d3abcedd86c20c5f1b6f30308a771ee4a27911f8b98a59754486
- MakerPaymentSpent: 0d7adfed60c3be36978ed291ab59f789ed02bbba1feaaa400691dfd66b4ad139
59e772233c49d00a48f5998727ed1617ec04a115f8806c8c07e511b232ce4c26
Both payments are on their chains and locked to the same secret hash 789872d4cc4be60582d3dc67cfe22c640378c45e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 83b46b96bfff62b08dc54b83dfec06d047c92aae1206250d4757511bc55c0990
- TakerPaymentSent · TakerPaymentReceived: 59e772233c49d00a48f5998727ed1617ec04a115f8806c8c07e511b232ce4c26
- TakerPaymentSpent: b0a505eb11704a3bf1890a5478560adee964d3c9d8f1637bacf6db5da7a478ce
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.