why2 reasons
mandatedestination_not_allowed
op 0 pays GB5VV62232HCT2CGE7EB5KLHMJEJTQKXDH4P3CRXA6KPYQOASK6MQXIL, which is not in the allowlist
counterpartycounterparty_denied
GB5VV62232HCT2CGE7EB5KLHMJEJTQKXDH4P3CRXA6KPYQOASK6MQXIL 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
- 8d51ad395c7a43cb056f659b1fa05939eadcd87fbcfa23bdddc274b6bf7126fb
- request
- ef3da5b3b14ac199508cbb16c3d19eb9536ca09c4cb90ff6c4b85b1c19c57fd4
- transaction
- 485e929933f9cc5e7ac2e5fcc0f6c101b7d6c77ffb7063aae3a3d55e5771840ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26151
the chainentry 26151
- sealed to the entry before
- 0bbd660a2f4adb4c26aef21d46eda295a923c58741a6b734ab4aeffd4dc04080
- this leaf
- c6a689860b01775d5f861639571554d41e15983c14f1741a12f610b7feef5aca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aleapOC1B2QFO93RZaXgVBOWHBgQqAf9/9THGj7Cw2cQ339wAC+ymE8r61AGF3H0nS9vPkkz2OQ+GmdAqnoeAg==