why2 reasons
mandatedestination_not_allowed
op 0 pays GD4HPZGVDC2I63ZDRSV2NBP5VF2UCPRH23PJDRQ2MUTDOWYV4VKQVGJQ, which is not in the allowlist
counterpartycounterparty_denied
GD4HPZGVDC2I63ZDRSV2NBP5VF2UCPRH23PJDRQ2MUTDOWYV4VKQVGJQ 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
- ad8f03e6c10488616ea5fdfc49d4eb2a971f26b9a3cdbe7038500dea83e33474
- request
- f578b3efa25e277e27ef22d762344d2a79a4cec325daa779842bdfd03dfe55fd
- transaction
- 9fb8927a5b260db548ea7d147ec35382361e8ed1ca0aa66f7ac997725433c829computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27182
the chainentry 27182
- sealed to the entry before
- 972e4fba8aa53672a6845b6068bdb73dd35b0de087062da8c982509ac9647ddb
- this leaf
- 6bfaa3c40164e0017fd386cef35b37c6110f3bf08d95d27e40ce465cd50454fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bk2luj+PoHPlQFZ8dzp1/fxHLAXgAuwedvTHZemvYllVFDHr9nwRqi7dQX0Z3gigTm/LgpuEr142BbBoAGVsBg==