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.
2102c7b391a56e6b9660f764ecbdec9a86aabacfe1b5ff9261fcdfc74c865d9a
Both payments are on their chains and locked to the same secret hash ffbda22b3253436394383e9008483f215f1dda64, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 2102c7b391a56e6b9660f764ecbdec9a86aabacfe1b5ff9261fcdfc74c865d9a
- MakerPaymentSpent: 742564f3f816137e29a77e5f1b308c23e1faca1c30e8f8459b5305e28937225a
7247ec8559e7e345190b3cdea4a44f1e82461568c24885f44e997eaea0ac4496
Both payments are on their chains and locked to the same secret hash ffbda22b3253436394383e9008483f215f1dda64, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b14ff711cf4d93330da8253e64d2b80d3213f5e16480445b9e581146b63a6302
- TakerPaymentSent · TakerPaymentReceived: 7247ec8559e7e345190b3cdea4a44f1e82461568c24885f44e997eaea0ac4496
- TakerPaymentSpent: f223a6a5b5b7cd0925570c45a52b682bfceb64b476d1b395f44305168f03cc9c
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.