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.
281f08298e0ed7ef265a3d8e5800d69f893539c2f7957d20616c7f352e2aa4c8
Both payments are on their chains and locked to the same secret hash 796f93d70885a39383d5ac421b3b8e5d52551b7f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 281f08298e0ed7ef265a3d8e5800d69f893539c2f7957d20616c7f352e2aa4c8
- MakerPaymentSpent: 1788ef181dca0cfa52d2dc587a53b40174ed1486a1aa60ddfdf2cb1e3ab3e03f
cb3065e30c05fec13b0f423cf0500de2aa1d4bdc8760ebfa115fa495ca75cc14
Both payments are on their chains and locked to the same secret hash 796f93d70885a39383d5ac421b3b8e5d52551b7f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7d97886495f6957907f9237b458bff0fcbb75dc81ad21e44bf9d592890c0f3a4
- TakerPaymentSent · TakerPaymentReceived: cb3065e30c05fec13b0f423cf0500de2aa1d4bdc8760ebfa115fa495ca75cc14
- TakerPaymentSpent: d6e8f64bc66e5b515502e6bc8ada78ed16080ae1f3225ec3ad1c679e93bca146
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.