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.
bb503bd941ce4808a34b619b9ef9f003e8181721b135804f288096738e3e8b55
Both payments are on their chains and locked to the same secret hash 608ef7491776e3c1260d2a0d8d6865a3dcd09d59, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bb503bd941ce4808a34b619b9ef9f003e8181721b135804f288096738e3e8b55
- MakerPaymentSpent: 22f04bdea25ff390182155a43c6489e5afed2f7ecfeb9481ec398ffad9bbec33
f7cb2e1dd5c1e6cc88408f6c9580e55f3dd5cf3fa7659098fe8c670aa5f03545
Both payments are on their chains and locked to the same secret hash 608ef7491776e3c1260d2a0d8d6865a3dcd09d59, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4e82d083440087c9507c823ef72feb0b3a54c2ceab8be50610f0c9dc0cdf6997
- TakerPaymentSent · TakerPaymentReceived: f7cb2e1dd5c1e6cc88408f6c9580e55f3dd5cf3fa7659098fe8c670aa5f03545
- TakerPaymentSpent: 85456d7cc7925064ddc180ebd849b1627a390db74fd0de6e412b242cb5b7dea3
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 defistats-gleec.