why2 reasons
mandatedestination_not_allowed
op 0 pays GCDAKE3YH6NBWNQW4LAUMRKYGMWDI4VVGEA3WWRQFVQN43ONNBZ7J25O, which is not in the allowlist
counterpartycounterparty_denied
GCDAKE3YH6NBWNQW4LAUMRKYGMWDI4VVGEA3WWRQFVQN43ONNBZ7J25O 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
- e836896ccbf3b53b63e89edb6c934b076b6a080ed8c305156d311c2650d3c692
- request
- 05e6e6f5ec81e71ae231bfa5cdbe53bd64b59830f5043a5ca309b33363cbe1ba
- transaction
- 9e50ed370cb39c70a7b28fc1df5a904d3d41f047f432622e04cbeb907d5d2a6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51184
the chainentry 51184
- sealed to the entry before
- e19657f11631cae55416fd69326952875155cbc5832b70d504430ada6ace49c3
- this leaf
- c8c5ba36a77526711b22a0bb0c333a920ec5ab42b4270cbb352cbec61b7c4340
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JLh01WV/950agbSXpS2A7EKqpV9Z8Ma7m/zd5Sm3lhBN38iKLWjd7vIz0ZvLg/v9qeXRW50nZ3XHoAySVyluCQ==