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.
3927ce120d0255f53510951eac0e478b7c5b0e16d1183a9956b5412e8a43aee9
Both payments are on their chains and locked to the same secret hash 80badb0e348d8877ea6a85870453c03f11bfbdd7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3927ce120d0255f53510951eac0e478b7c5b0e16d1183a9956b5412e8a43aee9
- MakerPaymentSpent: 064ec48cd032252182e27cca3422e2f4cf03b42f627f73684535d6bb68f63d6b
eecdd24222a520e8e60df334b751dede66b6026010cfe017d8fffde1911daf65
Both payments are on their chains and locked to the same secret hash 80badb0e348d8877ea6a85870453c03f11bfbdd7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ca612d345ed153878c0e9c725d7fa1c73865c2d32e86000a374583be49753c6c
- TakerPaymentSent · TakerPaymentReceived: eecdd24222a520e8e60df334b751dede66b6026010cfe017d8fffde1911daf65
- TakerPaymentSpent: 0383d1c63b0e82acf95ef2a6995d2a2ba0670d2c437f15a4a8bdf4bf371ff35d
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.