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.
36d80ce3a045a10985dc3bea3c85b3e06e39718f83c23f207961c560ab3a2df1
Both payments are on their chains and locked to the same secret hash 1dec304b124b805a02018e3bb839a80834000456, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 36d80ce3a045a10985dc3bea3c85b3e06e39718f83c23f207961c560ab3a2df1
- MakerPaymentSpent: 9343c90e4b166f5922825f5b599730b678300fb9f8d068f5548b052d27eb0661
884e2ff28fdce2143b1976734531333da5f2d1dd3cdc48da953c241f07377ce5
Both payments are on their chains and locked to the same secret hash 1dec304b124b805a02018e3bb839a80834000456, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e8efcbc6d349d47d92c362bef5af08ba15df92ae17bfed28fd6d41f86c66663f
- TakerPaymentSent · TakerPaymentReceived: 884e2ff28fdce2143b1976734531333da5f2d1dd3cdc48da953c241f07377ce5
- TakerPaymentSpent: 6c6854555fa60a41b702db7b1ff24a1e686924c879f461407dfa891fd8842f81
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.