why2 reasons
mandatedestination_not_allowed
op 0 pays GDVLTVJMKRI5RYMUCRRFDNE7FPY5FLKU6IW62RX5O2J5NMOKFS3ER6MX, which is not in the allowlist
counterpartycounterparty_denied
GDVLTVJMKRI5RYMUCRRFDNE7FPY5FLKU6IW62RX5O2J5NMOKFS3ER6MX 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
- 6b9f6c0eee750a2d662293dbe85d104a8aa6749ce8cdb4dc5f428f3933a538af
- request
- 13326338e8ce8e7ef1e1c6747fe36c51cc0de60979c1c28efa0823515a8ae63d
- transaction
- 805979dff98b21c931ac040d655bae87b99aa8ed2384ee37e3f3e85aa9719438computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77244
the chainentry 77244
- sealed to the entry before
- 52c52d8bc1000201c032d472df6605c142475a6bdadd0c42806b05d359553662
- this leaf
- 743fc16873b961cefbef76d8f4aa732cabe691e25a51c9f30b48b864a077b522
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- natPp+7/QpkRl35OnHkuytzXXiSckoM0twhccLZl1WL1+8Eiqa1Lmm8uUhFa9UljegU0XEk/8lCtzgZzSTt2BQ==