why2 reasons
mandatedestination_not_allowed
op 0 pays GDPWZZJUFG2FWBTLKXFFUWIHP7JQDTI2GHNEO56RAQQ4E7CEORGNSZVN, which is not in the allowlist
counterpartycounterparty_denied
GDPWZZJUFG2FWBTLKXFFUWIHP7JQDTI2GHNEO56RAQQ4E7CEORGNSZVN 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
- 9cda3435313c2c4379e0b04b031cec92fa259dc072f5d75db67d32775df909d1
- request
- b4baa009a8932fcbbe0d47e2d8e7d5ef91d1614e25ba87c16c1c53c8e29d09d2
- transaction
- ef7c83a0d05ffe403d2dfd80df88c98ae05022663d72a1689fc83e522d24725acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10318
the chainentry 10318
- sealed to the entry before
- ddea1a28b3948f14c80efbe530e463506025f51dfa8f9f7c775c3794a8aa946e
- this leaf
- 483ed9f861674c36a832545d69bdf2df4ec4de81ead1acf20095f9f544f8891f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- i3a1hWdGKdjXLS8ko6k38gdxfOpCUPpFCfAEd8omP+qMwoCzS0elVlTVXXf/6Y3od3kSDEb8kTDXiyLbrBWiAw==