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.
a2d8c2b7678eb6871203d4035f25616e688a79c43f2afbe288f44923a614eb3c
Both payments are on their chains and locked to the same secret hash c353111a6e76448e421b50577b7bb73a1decfbb0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a2d8c2b7678eb6871203d4035f25616e688a79c43f2afbe288f44923a614eb3c
- MakerPaymentSpent: 848559a7a14fc1af8aa15cfea00270288c32e8cc181a8def68c52ee986323799
3935be025ac0f384aeb323d01edb3e6ff70d4bb2b218513fc66789c765d74a23
Both payments are on their chains and locked to the same secret hash c353111a6e76448e421b50577b7bb73a1decfbb0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 84359e97e70a52d03dcee9d84172fc6aaf219583450cfdb020ddb95ebd94c820
- TakerPaymentSent · TakerPaymentReceived: 3935be025ac0f384aeb323d01edb3e6ff70d4bb2b218513fc66789c765d74a23
- TakerPaymentSpent: 0128417df0a12f2393c55d3e5797fb555ef811b3ea3878ae263e8c904b0b409a
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.