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.
1592daf8128f2ed29633825372fd559efb7d1b1bb5d056748114bad90002b803
Both payments are on their chains and locked to the same secret hash 955405f1f2c70960044b98bfcea09ee1d5a5a751, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1592daf8128f2ed29633825372fd559efb7d1b1bb5d056748114bad90002b803
- MakerPaymentSpent: 992ff4cde5b5262e412d86aaeb5853a678c2c4a17ee0be4321c4c55179be1f0d
5ffa134ddded452853ee657566ce5637ce5b02e6b6817f76af0013375ce3ba62
Both payments are on their chains and locked to the same secret hash 955405f1f2c70960044b98bfcea09ee1d5a5a751, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7282b7c170af24f9e81d8c427a657a6d557594ede75facfb4fcf36dd0ca9dfa1
- TakerPaymentSent · TakerPaymentReceived: 5ffa134ddded452853ee657566ce5637ce5b02e6b6817f76af0013375ce3ba62
- TakerPaymentSpent: 5a6f0c28839083ecc57081f709c00049f353c3fa382df0f321761ca53e73c95f
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.