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.
b40a576fa7a0b551ac5ae330d4c78deff433007492d6c1a02afa1e18613c4fe8
Both payments are on their chains and locked to the same secret hash b1f57bc5dbd0a8c2efce04e8c09d456f82b36395, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b40a576fa7a0b551ac5ae330d4c78deff433007492d6c1a02afa1e18613c4fe8
- MakerPaymentSpent: c8e47ca7f36d6b160f1d4baf81738ad52b96ef32ae680067778de565b2fdb0c6
b3aa68ce1c8df0a208a4c8b1b080632ec2d01835ca407353ce08e6c4e821f61b
Both payments are on their chains and locked to the same secret hash b1f57bc5dbd0a8c2efce04e8c09d456f82b36395, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cd2ccaa88c6b34075dd4dfb9b2216d6909b194e63e7100c1a277c534fec0a3c5
- TakerPaymentSent · TakerPaymentReceived: b3aa68ce1c8df0a208a4c8b1b080632ec2d01835ca407353ce08e6c4e821f61b
- TakerPaymentSpent: 8afbb13d49c87aedf2db67c63a61e5c8e3f2f41e484e3578fcd06f074ca38579
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.