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.
b622798603bb2c71d1fe1f15e48f0204f5947d72b219afa6cb8e985d893e68bf
Both payments are on their chains and locked to the same secret hash d6d0e27eeb9a0f6abcce130714f6727bc3b9fd31, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b622798603bb2c71d1fe1f15e48f0204f5947d72b219afa6cb8e985d893e68bf
- MakerPaymentSpent: 4449f0174e10f38bd6f6b41129be5727b8c7d354ab2908c069789d404937f278
a34aa663d4e12f895b0d4f2de255161a1aa973afc04438e914249daebd9aff46
Both payments are on their chains and locked to the same secret hash d6d0e27eeb9a0f6abcce130714f6727bc3b9fd31, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 823f8c9ea5fc97d0698a60f7ccb7fca5d09bc8da2f4a8ea134df7149fc25e9e6
- TakerPaymentSent · TakerPaymentReceived: a34aa663d4e12f895b0d4f2de255161a1aa973afc04438e914249daebd9aff46
- TakerPaymentSpent: 6a540a5a30da9f9b04f731da754c175a1827c15286a60e5266a1c377031b0999
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.