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.
f46f34bb129a185ea638cd35400737ec9712b15ae2889b2781a0a959ec781ea8
Both payments are on their chains and locked to the same secret hash e3481d2480c2cc302555d194783985bc18ae6ea0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f46f34bb129a185ea638cd35400737ec9712b15ae2889b2781a0a959ec781ea8
- MakerPaymentSpent: 64c33810092f33b51173ff833d3c7b61d3910d288897c3962aba1c03c8d1bdee
d40abfaf064cabf252de084230bf457878866f8daa750098a3af2d2cc980f462
Both payments are on their chains and locked to the same secret hash e3481d2480c2cc302555d194783985bc18ae6ea0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8ea7afb1a19f1785bf17fc8bb272872c14eac411abd94f08dc7b5f0637578d1c
- TakerPaymentSent · TakerPaymentReceived: d40abfaf064cabf252de084230bf457878866f8daa750098a3af2d2cc980f462
- TakerPaymentSpent: c9a5e60d8c31ffc9e07ea6a5e860856933172ee4a2e1e265d62cf75caa8f22a7
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.