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.
49b807f1546bc76547c7f7f85a099e93abd7b0d3e86269a52913c035598d0fd9
Both payments are on their chains and locked to the same secret hash 685c1638257fd5375da7e29b1955bab334f78803, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 49b807f1546bc76547c7f7f85a099e93abd7b0d3e86269a52913c035598d0fd9
- MakerPaymentSpent: e0bd714e4b54b1b314bf61bb86f87347255acb64bb78123b110dfb084debd90a
0270e1de6bf399b01dde33d7627172f4afcf2b747b2621efdecc1972129a36e1
Both payments are on their chains and locked to the same secret hash 685c1638257fd5375da7e29b1955bab334f78803, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4ff0491d67d28ca9804b22c1a3cb2dc704fadcce393490974585eeca0b384b52
- TakerPaymentSent · TakerPaymentReceived: 0270e1de6bf399b01dde33d7627172f4afcf2b747b2621efdecc1972129a36e1
- TakerPaymentSpent: 212c76e4aceba347b08fd920e2006f74ed67e7b17ec9d0ba639dfc094405668f
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.