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.
eea8b27dcb63ba8cd05879e5cb7b420f3112116d3335112e2b296d4b083c017c
Both payments are on their chains and locked to the same secret hash 090186da789166d24fe605aaa832b65b9e69f515, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: eea8b27dcb63ba8cd05879e5cb7b420f3112116d3335112e2b296d4b083c017c
- MakerPaymentSpent: 0874027491f9dbe1ff87cbe87c05d7855f6f4b95c89c26ba5bbcb774c81974cf
38d39fca5636b3b3aef7a27969076c0729c7421b1e9f6246818d6592adbf3bf2
Both payments are on their chains and locked to the same secret hash 090186da789166d24fe605aaa832b65b9e69f515, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d5d8b4e44fea6d95f947b330bdff7096c9ec26af48cd4dcadfd9a61b4f808138
- TakerPaymentSent · TakerPaymentReceived: 38d39fca5636b3b3aef7a27969076c0729c7421b1e9f6246818d6592adbf3bf2
- TakerPaymentSpent: 5e8290144ba469ee635c1098a8cdcfb9817ce199c1eb8603475933103be272c2
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.