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.
6b2e53af6865f9893a95e34771216d17c44604e1c7ff90a20c875119bd840dc6
Both payments are on their chains and locked to the same secret hash bc7c5643d916077507e1df2ffb1ea7f9e077e6be, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 6b2e53af6865f9893a95e34771216d17c44604e1c7ff90a20c875119bd840dc6
- MakerPaymentSpent: 842542911069118d50f8867c0ba7e7f0b41093b09935ac20177d4a093abc3a77
15cd15dc79b5c5cef3bc7e4d2b2050b471e07a42c9cf5b0b88761f4308e7c107
Both payments are on their chains and locked to the same secret hash bc7c5643d916077507e1df2ffb1ea7f9e077e6be, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 048d36a3e8736166efda09daed25e01a50a03b8aa86d8a6c73004f7cb6e30116
- TakerPaymentReceived · TakerPaymentSent: 15cd15dc79b5c5cef3bc7e4d2b2050b471e07a42c9cf5b0b88761f4308e7c107
- TakerPaymentSpent: 519efe817668f093140cb61a7d7a6413e05fd63aead2da0e9438b7ede2e5cdc0
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.