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.
231618671dc5c2e9bb76a7aea4e490595988388bbc03dbe85647f5df01df5fb2
Both payments are on their chains and locked to the same secret hash b04a5cb897e5a3ea000d0bc7b72641692e83d6ab, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 231618671dc5c2e9bb76a7aea4e490595988388bbc03dbe85647f5df01df5fb2
- MakerPaymentSpent: 98ac237bd629973b86f81439e398654e8837866cbe5ee33bfa48f695b67e63b0
b04a1c1c7d2f299c5f1c4c0331815a3d854357a69397dbb4253fdd0d8bac7c61
Both payments are on their chains and locked to the same secret hash b04a5cb897e5a3ea000d0bc7b72641692e83d6ab, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fef3f430e24dbae4e97d3304d46e8fd36c1dc5225ed6276c841a28aaa27c9126
- TakerPaymentSent · TakerPaymentReceived: b04a1c1c7d2f299c5f1c4c0331815a3d854357a69397dbb4253fdd0d8bac7c61
- TakerPaymentSpent: 3c56e725b8ac686535dc174418511b721c57b39d4e4d400a41bbd9ce4af89aae
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.