why2 reasons
mandatedestination_not_allowed
op 0 pays GDVGFRXKR6LOQPYJYZRXGSR4EJQB36HX33DHLW4X74P34QWR2N4GTCR5, which is not in the allowlist
counterpartycounterparty_denied
GDVGFRXKR6LOQPYJYZRXGSR4EJQB36HX33DHLW4X74P34QWR2N4GTCR5 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
- 5da071a513881718f3acac779bdc8a4f935a4c50807ccab8a75d1bc35bdb4070
- request
- 5b594d60de1ac71f3e35f7c247d1f9976eeab996a681f41dab905bbff55540c8
- transaction
- f51bdeee8fc0e32e85fa026a61f55935bc03c493dd711a65e42504762038aa6ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 717
the chainentry 717
- sealed to the entry before
- a243dd4c4d1dee2d47b675d071729fb1d4c614d12a3f0b2b8137873f2e0c2810
- this leaf
- 91d30146f938077b725755515dcbf71ee1e096aa76069a56af55621e5d03075e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UKa7/3jjuwLOafN3ryLZyooJWUWsbh2JMDGA+4z/5sKvA1govEyxehC7mNMIV0RhGNesSWctmaJlzN2PFohxAg==