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.
b404e2a3e8f883b977aa69e2856aaf70dc2c18e5d8ac47d1eb604daeeb7382b1
Both payments are on their chains and locked to the same secret hash a717ea6b41d95d8f34ecaa0f48eb21415c800dd8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b404e2a3e8f883b977aa69e2856aaf70dc2c18e5d8ac47d1eb604daeeb7382b1
- MakerPaymentSpent: 018d1311f565c0923deeefabe646d716ea387d5fe3d17842852db573b4b39ea6
b29c082c50258ba79387992f758abdd0e794b37d53982514b75511a0c92670ec
Both payments are on their chains and locked to the same secret hash a717ea6b41d95d8f34ecaa0f48eb21415c800dd8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d64af64114fdcff30c1cfb62e048fbd04184d80b8ee06ac6bf635b8d663e014f
- TakerPaymentSent · TakerPaymentReceived: b29c082c50258ba79387992f758abdd0e794b37d53982514b75511a0c92670ec
- TakerPaymentSpent: 7c34d7130712c034d9bd5b913d6a853a4388e9cd5fca27b51bd927406ab4b457
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.