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.
61b86db4ca609e2c14532e0ee62362663b58c7265bcdd1678a587bda28781eaf
Both payments are on their chains and locked to the same secret hash f83fe0ec484a6ead19251450fdeb0b6f2d492ba5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 61b86db4ca609e2c14532e0ee62362663b58c7265bcdd1678a587bda28781eaf
- MakerPaymentSpent: 797b6fa79dec12641f567de278f6e68d0834c8d1848b494f386da278d48eb2de
2d9433d2296ca5f2b3877496e76ce13bf687481fc6221aef2927dd6366000be4
Both payments are on their chains and locked to the same secret hash f83fe0ec484a6ead19251450fdeb0b6f2d492ba5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 58f47c027c753b848a01b70e61283a0a1920a93b8cb133368c794d78f33cd2ca
- TakerPaymentSent · TakerPaymentReceived: 2d9433d2296ca5f2b3877496e76ce13bf687481fc6221aef2927dd6366000be4
- TakerPaymentSpent: 96e0e4a66dc7a19670541041f79b01a3c5d96f12e12a7d8c685c4f3b3480e5d8
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.