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.
f7699848f08236fa82a1429e6b841a0834d475b9d676204269a07e18b6c74535
Both payments are on their chains and locked to the same secret hash 4bc74c297c77556df47569c3f3065bb138b28671, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f7699848f08236fa82a1429e6b841a0834d475b9d676204269a07e18b6c74535
- MakerPaymentSpent: 8f547b79c9ce199fc12f59e85759615b41de957c6d8c26311d60b27797049605
2efdb4b4847db439eeb3ae2f5548ff6e892b00c23742ac3bd6fec3afa799db46
Both payments are on their chains and locked to the same secret hash 4bc74c297c77556df47569c3f3065bb138b28671, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 127417579211c2ba940b2edddc95c948949ef94d7e19c99e7179d362bfdf3a70
- TakerPaymentSent · TakerPaymentReceived: 2efdb4b4847db439eeb3ae2f5548ff6e892b00c23742ac3bd6fec3afa799db46
- TakerPaymentSpent: 211eae6908c54c7f4c726b3cb80c52a48e2f2e4c50fcd8972184af5a91dd0827
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.