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.
f73736f60ccff69a6ff3443ac21283209fbe8fe1051b339b6225c54447e45cf9
Both payments are on their chains and locked to the same secret hash 9da24e551bf2b5974658ac1d76e2d754bfe0818f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f73736f60ccff69a6ff3443ac21283209fbe8fe1051b339b6225c54447e45cf9
- MakerPaymentSpent: 8ead61b55c7c9449fbc8237e3b6183b46360ff695db1d11ff71fbd25c750d985
e2bd52945208542790a86a42fca1923c84fcf7db208914f8fd03ca7c06dfc5d7
Both payments are on their chains and locked to the same secret hash 9da24e551bf2b5974658ac1d76e2d754bfe0818f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0c8f49ed02b1654103e8db57298afe738d302cb337fc69635106e933d3fe4841
- TakerPaymentReceived · TakerPaymentSent: e2bd52945208542790a86a42fca1923c84fcf7db208914f8fd03ca7c06dfc5d7
- TakerPaymentSpent: a05383273fa9a9d8a1048eadc8f44b42ad63fa5c2c16b52a0a62fd6724eaa330
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.