why2 reasons
mandatedestination_not_allowed
op 0 pays GDEWL5ZVGDKLRVBQGAXYSITUELGAWSS7ZMSIWVWUFQO7FLC63CWH6H2P, which is not in the allowlist
counterpartycounterparty_denied
GDEWL5ZVGDKLRVBQGAXYSITUELGAWSS7ZMSIWVWUFQO7FLC63CWH6H2P is on the screening list: you placed this account on the screening list for this run
what it was decided fromfingerprints
- rule compiled from it
- 8829452c7f231f29670b79d563f30f7f49e3de8b85b356dde6eb9aa6442c9f11
- request
- 73b53ad5769226de26242940d6e042e106eb10ba91e726f26a28d9887d430891
- transaction
- aac5f825dcd4405001a4d675f809cc3eb1ba2fd3ea763e72764fb7eb7266d5c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10073
the chainentry 10073
- sealed to the entry before
- 794af8960f120e6b609fcd65301cf729be068901f07a1880109653511b7b24ad
- this leaf
- a19da255505be580d14bc356ef31ebbe1987736cc3e00f5b85a736bb93d5ae9a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- k5zKQ2n62ZMr/zfZtVap+rz/OiK2bHuPhEoPOQvUJxDl1Wyj4G3FqTKjeZx0g8cRc5Ka3zNtbJRBZfho5cwWBg==