why2 reasons
mandatedestination_not_allowed
op 0 pays GD6SRU5OQPV6FWATB6KIPGTOJWNLKKO2EC2CVTHFJ5NGY2EMFJ6SJ4LA, which is not in the allowlist
counterpartycounterparty_denied
GD6SRU5OQPV6FWATB6KIPGTOJWNLKKO2EC2CVTHFJ5NGY2EMFJ6SJ4LA 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
- 03b0f7355b3b8bda0b5e563b88f3b24f8efd02f81b196b08a44c85a0d7b6751f
- request
- 122067cb473b65e7b4e55d7cf938a710bc1d7af3985b64b92ba05cbdba45a5e2
- transaction
- c3db243f14c5efe7a5083a1aa4e2ae920f164a101dfd7a6744e98737766f5dfccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40841
the chainentry 40841
- sealed to the entry before
- f374d196b4c706ab26b157f8019aa417badc186a858f5255d7e6a2ccbd9e04af
- this leaf
- e132b0db39da86ea52795f86f420063b4e982347eecb7579e44a92c3c237e454
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hMsfU2sNZWgA42z6eCk0XC1f0w5Awl9mJx0IhevZ0P6XRrq8dXovmGE7jY4beii7B3QYdv+cGstFA8JrWZDbCw==