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.
59f610a8ef8fb545b209c3fb8d972aa72b71eca8893720664aa3924cdda53e89
Both payments are on their chains and locked to the same secret hash 2694dbec1c9286cd82356c8f717c0067442b3842, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 59f610a8ef8fb545b209c3fb8d972aa72b71eca8893720664aa3924cdda53e89
- MakerPaymentSpent: 5877947f65e4eb4ef8ca6a27a654f27ade106aaf36e23d55313729691d421128
7f5dcb3dd7bb239d8cac9ced96cf8be9fa46f3fbecec5947b3b240ec954c4007
Both payments are on their chains and locked to the same secret hash 2694dbec1c9286cd82356c8f717c0067442b3842, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58840a97d5470a64630aeb56ba5d4f2361323ba66cf1650065b1bc2dc356ba97
- TakerPaymentSent · TakerPaymentReceived: 7f5dcb3dd7bb239d8cac9ced96cf8be9fa46f3fbecec5947b3b240ec954c4007
- TakerPaymentSpent: dab5eb89a420bb28a8fda5ab7d6216757d23c539e8af97ca35873f5438246aef
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.