why2 reasons
mandatedestination_not_allowed
op 0 pays GDNAHDTCIRZEFBTVW6TQW2ABVN7ZHLVAUGYJIFFXSPRG4MS6VE3A4MC4, which is not in the allowlist
counterpartycounterparty_denied
GDNAHDTCIRZEFBTVW6TQW2ABVN7ZHLVAUGYJIFFXSPRG4MS6VE3A4MC4 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
- 9970ef5389669a3f69be2bc20e0261c6988b28953a5f0f0668c70bbd2407ddef
- request
- c5c785c607f5789e5a8f42a1f1d68c4166ccc11733f43957a3018a534d88c4c2
- transaction
- ae51f2ecc2e4feb23865ebdd21fd1ba3f446088f5ccd52b9ad48c40460513470computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51408
the chainentry 51408
- sealed to the entry before
- a339f729f09002dc83b5a0dd31f9f357ac821caa8b10514176d1b243ceb50877
- this leaf
- 9194ceeb07f902ea1e739c754dc10e31d2b1b897189adc74cec9c47cfd622193
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0C0CcTnODMl992giLvuoGOMUf574O6M9gs4TzmhznlwQasboG6q7a1jTvmrThXnZ8TKheYx8KdBf5a8VgyjEAg==