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.
224b1e4fca49e325b863892f6a64f5a15988562fb8f01ad1baaab3f6266356bb
Both payments are on their chains and locked to the same secret hash d900bda612c9518ccfbf70e77eac632871423901, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 224b1e4fca49e325b863892f6a64f5a15988562fb8f01ad1baaab3f6266356bb
- MakerPaymentSpent: 9b54ec1a47c910f62f9e045a9a94fc1c5f6d556240bc4fef96d3a07d1fcade96
0d8e4f6d123a3bc4ed58f452df90d5c3c9f766c1ea0020f6fadc185d640445a7
Both payments are on their chains and locked to the same secret hash d900bda612c9518ccfbf70e77eac632871423901, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c66bd1d09d5d6cfb2bd12faa495c08f029f2eb291c38bdfba9af17b9af3a5300
- TakerPaymentSent · TakerPaymentReceived: 0d8e4f6d123a3bc4ed58f452df90d5c3c9f766c1ea0020f6fadc185d640445a7
- TakerPaymentSpent: 93773b77b2345a99ca0c5e5b5980ac5bb79f1491d454f89719cbf8c32822be7e
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.