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.
4f36e29155743105b1dbbcc7c43170ded4b4946648a673980f4aaccf41a01207
Both payments are on their chains and locked to the same secret hash 5b9ffd2c45eaab1ff89448dfe816c615914bb89c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 4f36e29155743105b1dbbcc7c43170ded4b4946648a673980f4aaccf41a01207
496835ec4c74ea328aa50a70052192054b4eb4c5d16ffcffd082b97ecddabd6b
Both payments are on their chains and locked to the same secret hash 5b9ffd2c45eaab1ff89448dfe816c615914bb89c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: fd54817a0f5064dc21608c7ed16e2daabcad7743f9313f3e50d14fea5d346669
- TakerPaymentReceived: 496835ec4c74ea328aa50a70052192054b4eb4c5d16ffcffd082b97ecddabd6b
- TakerPaymentSpent: 8483072ad07b7b2c51ab8df851558a8bcc1dd2fa7c8da9ebb69a03ce94874098
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.