why2 reasons
mandatedestination_not_allowed
op 0 pays GA5HCEZLOZPEACN4XHZ426CDLRIM2HRHEJ4E7SLFHISRKWG623OHQS4D, which is not in the allowlist
counterpartycounterparty_denied
GA5HCEZLOZPEACN4XHZ426CDLRIM2HRHEJ4E7SLFHISRKWG623OHQS4D 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
- a691acfbd47df1d014c9a95b9c629d61b429f46c98cc17455845ecf08be6e27b
- request
- 4ca80aa1c99a4d9a0ae14e741cd8417a7eb2987ea2c9d8266c6c9a232d429f1a
- transaction
- 0051ee0ed181fc0e4a505c6993caf2242913337426b014a966cdd6e368e8b993computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 377
the chainentry 377
- sealed to the entry before
- 04938f036d27dd0764eeec89a28cc74acdb1a98133c57dc06ceafb2af97b8968
- this leaf
- e30ae98448002ac3495bbe679b563d36e5a3fa3753b8716d02d3ed27a425838b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5maXPk0DzW3SlSy4r3QE+aqdTOZTVf2r9ECFcthJ0Li0PbTzeKgA+EwJFtANdO8SIyZwn9mb+GiiT4J3dCbsBA==