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.
90df3e1772ceae42423f784701185b991b2482e24b4696d7dc9c149198e1d1de
Both payments are on their chains and locked to the same secret hash 70d1cea592483d3a6415788e1fc145d2eb527544, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 90df3e1772ceae42423f784701185b991b2482e24b4696d7dc9c149198e1d1de
- MakerPaymentSpent: fa348c8edc829125fd0140e1038cef0b2e65429d387dc61fe60bda87e07f5eee
4a3833f3c8540cb8b78ced12e9523f7ac63c7525ee224e6b2d915e1d2ee41b4c
Both payments are on their chains and locked to the same secret hash 70d1cea592483d3a6415788e1fc145d2eb527544, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b95851142f4b22197a3f392b7e2e329ef34258b174a10259928f90deededd920
- TakerPaymentSent · TakerPaymentReceived: 4a3833f3c8540cb8b78ced12e9523f7ac63c7525ee224e6b2d915e1d2ee41b4c
- TakerPaymentSpent: 510fc14d5dc5a9aca50fc5f2f1ff6c8d5d34fb276d344e0e321b6b1dc03139d3
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.