why2 reasons
mandatedestination_not_allowed
op 0 pays GDLEVU4RCX73HHD6J32C4ZAKKVXWZCURZK7TXYOGYQRJDGV4SE5LK3PQ, which is not in the allowlist
counterpartycounterparty_denied
GDLEVU4RCX73HHD6J32C4ZAKKVXWZCURZK7TXYOGYQRJDGV4SE5LK3PQ 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
- 06d1a9a2e229f96165618aad618de6bc7268f88782203a03734ebb5ec74436be
- request
- 21e81740ca10b80a0dffaeed0fe1271c9155603d5b20ad0cc9d2cf8263f862ba
- transaction
- 4fd808bf29b2cd8f8629223eed7df09ba8192b9d0bdfb8adccb8f88264c14c39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34132
the chainentry 34132
- sealed to the entry before
- 52e7b90d9e09f989270a97d360aeb6a54e31d35eae0afab81986c607cf9a8487
- this leaf
- 0cb2411e4b6cfc41b6a0f6c634bf37501f6b46c185a752a0d87a8482864809be
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uMazBRCksQh8421FuW1PWdDlZbOxFim/DhCJSFJXmUr/NXyjnt2YY7gxn1T7M4syT1qTMTRJCFvdZCMqLSC6BA==