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.
8e61334f0acb68e2a7e92b13a58e04ea5a2117ec7a669cb3190a5bb1fd3f54cc
Both payments are on their chains and locked to the same secret hash 1f9c287afadb4e57d08b2d0eb12b3f3e836e6d0b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 8e61334f0acb68e2a7e92b13a58e04ea5a2117ec7a669cb3190a5bb1fd3f54cc
- MakerPaymentSpent: fb80f6245f1f2ad303d050759e8545ccaed59b9da16fafe5016987937d4abf5b
1a17d6f3d56da59fded4369a1558ab6cd30818f0746e5b5e49b25907f7798e91
Both payments are on their chains and locked to the same secret hash 1f9c287afadb4e57d08b2d0eb12b3f3e836e6d0b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dbb01014c9362db75167209f2eafa02801bd9e25b2bd5db31b780cf8f2b7ae3b
- TakerPaymentSent · TakerPaymentReceived: 1a17d6f3d56da59fded4369a1558ab6cd30818f0746e5b5e49b25907f7798e91
- TakerPaymentSpent: d36fa182ce8dca1384abf74e941436de875ea1b6f75a476d874562ccb2a5860d
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.