why2 reasons
mandatedestination_not_allowed
op 0 pays GADENXM4KJYQVE65YPD2OBAE43KYEZO3R3WE3BSN6F2WPXMEWJHUXWSG, which is not in the allowlist
counterpartycounterparty_denied
GADENXM4KJYQVE65YPD2OBAE43KYEZO3R3WE3BSN6F2WPXMEWJHUXWSG 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
- a15593ac6554204055533dc91acbbe3fd70bbb164c45784dfcfd285d7ad457aa
- request
- 015a12927db3a07ed5892e3de5ac5c375c149f019cf14f34fc6b86585fa78447
- transaction
- e9b4a577f6ae5a30426cb87678df66a6a39d9a8d4ed484ded308367cc7930394computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63664
the chainentry 63664
- sealed to the entry before
- a9c631b0bc385ef065728135051b1cc5bdc2d6452bc636e01314cf6d3550f01e
- this leaf
- 7f9dabd03ec4825f0ab714ce8bdc456f9aeeeae2096c75c617b82c03190661bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lh7L0czRGpmBka2A+utxWesbjq87J+5vycCTac3rXxJnUosWi7/vsBwZL8SZ2SKzYpvvov3dVeJGWEhBFzv9Cw==