why2 reasons
mandatedestination_not_allowed
op 0 pays GDBIDFQIOP5XO4G4TZ6652JJCIQT5X3MADDP3YMPM755O2KMKDUKJEH5, which is not in the allowlist
counterpartycounterparty_denied
GDBIDFQIOP5XO4G4TZ6652JJCIQT5X3MADDP3YMPM755O2KMKDUKJEH5 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
- 3a61af3588fc4c03d8fb5f28300a85b2dbaaafd0efea35adb42d1cf661cc83e1
- request
- 50791d44ca762766dfd09438786a7b5ae5ea4dce03b7fa839bbddb69f5b17eb1
- transaction
- 171834b62fb8b060b18182f3230b08e8f16f4471e6a2167a2a45d76339121cc7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47599
the chainentry 47599
- sealed to the entry before
- 7ec14e7d293d7bdc7ab60e9b9321e2007105bd4131795d991bcd188c7673bcf3
- this leaf
- e43adf23ef0c51be74dd53c29b89ff7cef23e7e8dd2854c86241d0c1208498c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wks9P9A86e+5YfSc7QeC/tD1S2CayXU0OvwUtHPSY3mArXAE59qlW0JeRg0uk5q5VOSEScICBLm2h3vxwNGsAw==