why2 reasons
mandatedestination_not_allowed
op 0 pays GDFYBUGIRHCA6ITMNH7L47N4TC3ZIWQCR2V4XXB7PJN2INT6VONHRUO5, which is not in the allowlist
counterpartycounterparty_denied
GDFYBUGIRHCA6ITMNH7L47N4TC3ZIWQCR2V4XXB7PJN2INT6VONHRUO5 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
- c5da29bf9a0f3765363d16eded11a1840e2c027b820fe6b3dc6c947001c5333c
- request
- d7592fe7b7e14df46e30e719da83c5bb993a966a32eea555836f47898214f842
- transaction
- bae9e843459bc5999e3c1fcc44df9abf2b7d247e98cab3318f2055bff9a242b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 132
the chainentry 132
- sealed to the entry before
- aa18758319d4c1ed93f1e5344448467e6835ad4c1ba387cb97328e8c814cba42
- this leaf
- 734f0bec13ef77d8f0e463806e55f84d3be1911cf97b71854d17af7c503f6b9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8VrrprE//eQftaUbglenlI2CBN+2T3BbJMllorYUkQwSS7M+bRspUodqNGQ/6na8imhuqWfFXAqOcfZ9FAGmAg==