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.
a2d08a86d887ae6d657811976a48580e982811d05ca45a42e88ff79c528c848d
Both payments are on their chains and locked to the same secret hash feb32a4e19e037732bd23b5a6c64c2a7b65c8a25, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: a2d08a86d887ae6d657811976a48580e982811d05ca45a42e88ff79c528c848d
892147787b56be029b2c1c5e3e230e25a37065790f84d41ca353ea013e246894
Both payments are on their chains and locked to the same secret hash feb32a4e19e037732bd23b5a6c64c2a7b65c8a25, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 7eaeafd8fa64b4beda005516432a4ede89065d4a23135ebca511012862a8339a
- TakerPaymentReceived: 892147787b56be029b2c1c5e3e230e25a37065790f84d41ca353ea013e246894
- TakerPaymentSpent: 290b2546409cadb67e85924670a4dd406f106aa4f068292ff74a01d75090192b
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.