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.
5f5cee79162fa458f737c45317412384efc7baf1998d8e6f85a34b0b40e2b7d0
Both payments are on their chains and locked to the same secret hash 87372fcabaefa35a5b867884377f02a022450b25, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5f5cee79162fa458f737c45317412384efc7baf1998d8e6f85a34b0b40e2b7d0
- MakerPaymentSpent: 99c282295deaae3f8a48d8fcd4c262630bf0857f3d07fc2467cdf3da26bafe77
24318623b9277aa65a82cfa54a919ae6a49ca25eda6f140935448e5dd8015165
Both payments are on their chains and locked to the same secret hash 87372fcabaefa35a5b867884377f02a022450b25, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ec6791ed30480d23b49155b23b6cde151eb6ea573dad32135f717a56638b6745
- TakerPaymentSent · TakerPaymentReceived: 24318623b9277aa65a82cfa54a919ae6a49ca25eda6f140935448e5dd8015165
- TakerPaymentSpent: 3c7cb3fbd07d6dbfaa57c7967096962d8ebe87970557aa07f4c0eff5b2e55ec6
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.