why2 reasons
mandatedestination_not_allowed
op 0 pays GBEYEQZKPLFRC3KQ6UPLRILHBUMYMU2UCJMWQWYDUVJSNNGFVZAGB2V3, which is not in the allowlist
counterpartycounterparty_denied
GBEYEQZKPLFRC3KQ6UPLRILHBUMYMU2UCJMWQWYDUVJSNNGFVZAGB2V3 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
- b66bc699c69b35232bce2156e02e1ccd61e862d53ef525ac2171f043014b160d
- request
- 1dc52d228151005152aecc2a26321002a744407445fa527e63b14d1751b592f3
- transaction
- c5eb5e71b4ed0c7273d5cacafba1d2fe44a916a5ec1f481c4a6fb0b5d4f17381computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10663
the chainentry 10663
- sealed to the entry before
- 0c337fa3e87a430c9de1245bf26a8cceec06b43b0a267a7274015feae5050528
- this leaf
- 0cb1487114d4ad617d85ffb7095ce5f450eb89644201db1d1b767b8758bf0823
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CBOAlsdngA41693iTNQyLX8kCTUqc7S109d2r2NNLUs1HdTO2otO02uO39FUSJTmcha/YUFTxVnT6v4YDxZVAw==