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.
787e41776fbdf1294322d7446239b7b704b31c4d17aab3024839fab94ea874c6
Both payments are on their chains and locked to the same secret hash 058d0d2be41aa95fcfe89c2d1a0a84b8fd88f61f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 787e41776fbdf1294322d7446239b7b704b31c4d17aab3024839fab94ea874c6
- MakerPaymentSpent: eb0538deef6595cca08c574df0a4544d77437debaedf8aa5a4ea82518bfdbfde
bb24e4f9f5c1d609e331e65ef1d5b9f9a858ebae3e35335d7f4e4aedf09d0091
Both payments are on their chains and locked to the same secret hash 058d0d2be41aa95fcfe89c2d1a0a84b8fd88f61f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 40b3255f14b54bb8bfb6a64a23802ce5e77ff83b3ad4f9c4fa17c167dc6fa9c7
- TakerPaymentReceived · TakerPaymentSent: bb24e4f9f5c1d609e331e65ef1d5b9f9a858ebae3e35335d7f4e4aedf09d0091
- TakerPaymentSpent: 8ef8ad2abc09f80e3912fde33ba083d729543dcb7fbf09cd308ff8a42d501455
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.