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.
77497ab3633d3358433a0c0f558da28caab04ad57bab74ebd302af5590b6a08f
Both payments are on their chains and locked to the same secret hash 73e19fa44d872666391643a137031122324a5dad, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 77497ab3633d3358433a0c0f558da28caab04ad57bab74ebd302af5590b6a08f
- MakerPaymentSpent: ef4519fd6b2586024f138bbc70a5291dc15cc10bbc4f6481d0ec5d7027bb5df3
5dfa2abe826c4f8b07e241bcb028bcb0a2978d5a54bff140e735a0c139f28d48
Both payments are on their chains and locked to the same secret hash 73e19fa44d872666391643a137031122324a5dad, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e172afc17f13230bcef5b232212e09b6d78d5531de5bf0c8df208543d260c761
- TakerPaymentSent · TakerPaymentReceived: 5dfa2abe826c4f8b07e241bcb028bcb0a2978d5a54bff140e735a0c139f28d48
- TakerPaymentSpent: c9f16e308dd4d2caec102145c3424071ea43f5000015006fca9d2d0b6fce93c9
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.