why2 reasons
mandatedestination_not_allowed
op 0 pays GDECEZFYJMM5TBRWE2SFQELA7O5OCF4VMUJ5MB5EQNZD4MS4OCKVXSPU, which is not in the allowlist
counterpartycounterparty_denied
GDECEZFYJMM5TBRWE2SFQELA7O5OCF4VMUJ5MB5EQNZD4MS4OCKVXSPU 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
- 8d40f3622543232f222dd2c647d079f0a2cfd0c6acd6c62c789ddec354ea4b22
- request
- 484309e779733ed8edbcc392da91bb070e2875ea687d30fabf6c98ffcd1741a7
- transaction
- 0863d4722ff9e5d409a90be3027c28b9932b0b75600c87cbce4e1c9a6ed62291computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1276
the chainentry 1276
- sealed to the entry before
- 73bbf1b3cd0f91f0db8737228271bff6ab8d36c1a9d4fa0d3376d5f0264760cb
- this leaf
- d9221966a4dc7121b5a62ed8b976b337155ed26b8cb5dca47e1a3302d9fef590
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pQYwqUtfqNawvbtVgTLQH1K4cdUzqB9QcVLACIlG8ZFdVpcenNBZp3iGSD01x/FWwfUnA5vzNDs3vd563bFsAQ==