why2 reasons
mandatedestination_not_allowed
op 0 pays GD3VCUTF3PLLV7AWND5Q4K454X4MH2NMB3E4GGSADI7O2HG6UVOWMW2F, which is not in the allowlist
counterpartycounterparty_denied
GD3VCUTF3PLLV7AWND5Q4K454X4MH2NMB3E4GGSADI7O2HG6UVOWMW2F 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
- 7c29858771b70a4d190b231434334cbbdeaaf743f11f987379182eaf0ccb1e2e
- request
- e82be69f0ced1179239eff2da3696208264f30dd6d5b1eb3c19e28e57bd49411
- transaction
- de320c7d7addd1ee0ae7a794fee0a4b3bdd72eccae0094b1c3d5d6045f0b9c03computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70134
the chainentry 70134
- sealed to the entry before
- fe6b7174fd8d6bb519b131fce22adbf1704f9617b7ee85639ea2830e8186b9f2
- this leaf
- 055048ad9c634446edf998a9006a8caafe004f7827a7e17c4552c8b2f62e0d38
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e25LzD45692BU20rsy8jd/SvZAsKouwPNZ4MAPN3lEGQRh5eyrFgvPCSGFAqZcnQA3u/DjAPlRdqzLibukzvDQ==