why2 reasons
mandatedestination_not_allowed
op 0 pays GDLM4CSL3C4FN7IDL77M3V7P23MMMNROCSBBXEEDH7CI2BDKZ725E3U6, which is not in the allowlist
counterpartycounterparty_denied
GDLM4CSL3C4FN7IDL77M3V7P23MMMNROCSBBXEEDH7CI2BDKZ725E3U6 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
- 4fa3914f26b5d4620dcd9d2b36812495b5a87c0fc2888b493f7e74a639b66338
- request
- a17c1eeae6cfca53dc35a1b2845151995ed8ac4d12963f9ba33c3b6877a22f42
- transaction
- d5317e2987f6ad2a2c186f8e4f1017960410861f2d116ae49029f9143e9ed383computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25166
the chainentry 25166
- sealed to the entry before
- 177824deb16c43f45770aadbb4909558f1e873aa7bb154533b8960468d688a6b
- this leaf
- 999bab700cd0d3f7edeb4a1b20b11486cbc77a062b3d74adb6df9b3476a6ef66
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AQ7GefHZ64C1pzZFwvzYOIQVaCJ/NW+4gAeHnlMWBXe6XJnLuCI9QZ7TdIuJ0A7GWvI7yZijGVbOBE+NUX6TCw==