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.
41c2a5085e2f3ec02ab6c42b4fe323533a38fc95ab40a3fc5a00a6e870a06e8e
Both payments are on their chains and locked to the same secret hash 54d053b64ac2e7fac92a3642014c9e7c179447d1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 41c2a5085e2f3ec02ab6c42b4fe323533a38fc95ab40a3fc5a00a6e870a06e8e
- MakerPaymentSpent: 61b66719ef7186130851c3a33b129d2c50607333987a91ce59456e856b21202e
46833d8a68f7b6db8b37c8577a25196d75dc5c0abd15c477b63cd3796e4cfcbd
Both payments are on their chains and locked to the same secret hash 54d053b64ac2e7fac92a3642014c9e7c179447d1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1fda2a718f1a9a239265ecbdf9be44d2a92a3799d2b52531ec9d8f2c96a1724e
- TakerPaymentSent · TakerPaymentReceived: 46833d8a68f7b6db8b37c8577a25196d75dc5c0abd15c477b63cd3796e4cfcbd
- TakerPaymentSpent: e2ddaecdb5396ce230fe2fbd1009bd21cc799acadb6a444d35f220f29dab14f4
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.