why2 reasons
mandatedestination_not_allowed
op 0 pays GDL4NYKM6D6DZ2KELLSJPJ67XDVPOMVUWCKX44VNWPXAFAY2PYS57PED, which is not in the allowlist
counterpartycounterparty_denied
GDL4NYKM6D6DZ2KELLSJPJ67XDVPOMVUWCKX44VNWPXAFAY2PYS57PED 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
- 1399a9e3d85d69d0800ca58c4cb6c602cecc74aaf4ee010fcfb6ab044ca95db6
- request
- 388670343c9ddd0d6729f56e510383c9c9bc618afbd7568106fab21e524e886d
- transaction
- 30de59b41975b73fe4f8248075d310fe1e293162f8e5d7e0b60b414eb58f6608computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37080
the chainentry 37080
- sealed to the entry before
- dd2b81a65830b76a522e2d196b5f5dcd3a37d4a3e80a3e2fba9af0dc72cf480d
- this leaf
- e42835e10241ddae943a4f3db0e862cefe6bf5f14fc78a56bab0fb8a9792464c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Wso3dF/mITaNZJJmastspo9Sel4EW/txW+5Ic7HPVBOcuFkXXJwAVGColkbmciUddyg3yCKwcAVyjWq7LsWIAw==