why2 reasons
mandatedestination_not_allowed
op 0 pays GBBD7YCVRF526IAJ37SVMHY6YOBR3GNBGGTBW7BDV3SDNHUXOZN5CTQ5, which is not in the allowlist
counterpartycounterparty_denied
GBBD7YCVRF526IAJ37SVMHY6YOBR3GNBGGTBW7BDV3SDNHUXOZN5CTQ5 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
- 5f9131bac6f577626dda669ae394e3bb2913b9d7ff8d0b8967aaba1c47728191
- request
- fd35979e8b14560f3cc6d816447cde2123f71c35ac438d21d471419e325b9e65
- transaction
- 9c9163ce6f900e31550de06cd25af746f301f9768a6d7352e7d05a55052f85a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62813
the chainentry 62813
- sealed to the entry before
- c2c031fcfae0e289a1bdccf975436f7915fc0fb6714b0e699baf883be9263529
- this leaf
- c9ca2a79c135d5cddd3053e98adf0678dc0aac80fc06c80b0f07f96083d88a3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BF67ALXqEOTOMOTKEdlGYS/4WL/ejMNPnAbpLwCRsehVSFTJJd6JP2NkSf+tshYy9UrPwr9Ni/PjGZy8rfM9CQ==