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.
6e9dc7334b71adffad5d2bcac4a0eb39442d4baf6775e640db5da3614ae11c68
Both payments are on their chains and locked to the same secret hash da843d530a599b8cc0202094add1092501496e7b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6e9dc7334b71adffad5d2bcac4a0eb39442d4baf6775e640db5da3614ae11c68
- MakerPaymentSpent: 6957662effdb772db87d5ef9d127c0ddf60d1da16e571a937d77e46ede05e198
e5bc0d9d5687ac237dc2182825760c6ddf1466fc00aaa52fe6f0e99034930655
Both payments are on their chains and locked to the same secret hash da843d530a599b8cc0202094add1092501496e7b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 62a15ec359d9fe27f6251d925547dcb9fb4445e2eea00e4e9491846dfa5ad0ea
- TakerPaymentSent · TakerPaymentReceived: e5bc0d9d5687ac237dc2182825760c6ddf1466fc00aaa52fe6f0e99034930655
- TakerPaymentSpent: 81e68f84330462819afd2581858116bf33de56554d26ac86450776e1f97c21a0
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.