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.
d4e0a44f7141601069046f11368fa4755f1a99fe65510401261101ba917dd838
Both payments are on their chains and locked to the same secret hash b74ac7a5e312681ded51fcad976a05ff30c0266f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d4e0a44f7141601069046f11368fa4755f1a99fe65510401261101ba917dd838
- MakerPaymentSpent: 6d6f3247cea747045f2b0302b0ef56ccfdd284223afa1c10782ada4918c8b6eb
911843da2905e42174e3eb418b70653b987fa8cfe2a6cb8385525c60680df3ab
Both payments are on their chains and locked to the same secret hash b74ac7a5e312681ded51fcad976a05ff30c0266f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 796db8a58a0907e6e3ded27b419628f242a8295d8c0dbb9440e79ca7cf048ad9
- TakerPaymentSent · TakerPaymentReceived: 911843da2905e42174e3eb418b70653b987fa8cfe2a6cb8385525c60680df3ab
- TakerPaymentSpent: c599d8b2e454cd243caf5d882cadf2d1427ba918300acbae307d4f30770ea68c
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.