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.
1f34b7019e6ce27e3699a263a5fe6b2578311077105d60f8c6a13197b6427a73
Both payments are on their chains and locked to the same secret hash 041a125fa135ffb5ea0d2563bd02a94d50897244, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1f34b7019e6ce27e3699a263a5fe6b2578311077105d60f8c6a13197b6427a73
- MakerPaymentSpent: 1673bb467e500a1c116cbbd9584251738b52d57f013a7eb6cd22434c18dbf5e7
3f186e0a4a778c8749150317048c2f9ec6a107b5ddee62faa812a37f15017077
Both payments are on their chains and locked to the same secret hash 041a125fa135ffb5ea0d2563bd02a94d50897244, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 35a93fb5e455e061a1b234e5c909b34682a053551aa12ceb774cef449854ccd9
- TakerPaymentSent · TakerPaymentReceived: 3f186e0a4a778c8749150317048c2f9ec6a107b5ddee62faa812a37f15017077
- TakerPaymentSpent: 478fd59a6ed7b2d7446e154ca81864278836c5ec161b1ae26a4be5cba4f1f9cb
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.