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.
29165873229f9b319fcff8d9c494502efc47d67795d06db7de71980114cb45e4
Both payments are on their chains and locked to the same secret hash 9251facf78641b2242fbf697d3ad5b05d64d02cb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 29165873229f9b319fcff8d9c494502efc47d67795d06db7de71980114cb45e4
- MakerPaymentSpent: 42d045154a0c46114317e3c9c39b01975236294b472b5663389eb605074ae52a
7bc49c8efc7fed7cb8a0320f6ba67df6a9bc74a398598818a66bc3b2db7a43ca
Both payments are on their chains and locked to the same secret hash 9251facf78641b2242fbf697d3ad5b05d64d02cb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2c9928429cf13ca5dfcd9e7b1fd024bbce02fd09e2f4fa861117b636b179d6d3
- TakerPaymentSent · TakerPaymentReceived: 7bc49c8efc7fed7cb8a0320f6ba67df6a9bc74a398598818a66bc3b2db7a43ca
- TakerPaymentSpent: 850cd71ab86ad6764624bb2dadea3518180315d42472a4849a96368c1915a549
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.