why2 reasons
mandatedestination_not_allowed
op 0 pays GDIQRJMFQDN7SQQVTSY77APYWW6SI2LTPIX2IAVTXBHIMK235HGKQQWX, which is not in the allowlist
counterpartycounterparty_denied
GDIQRJMFQDN7SQQVTSY77APYWW6SI2LTPIX2IAVTXBHIMK235HGKQQWX 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
- 9a96d61a6265e8e7686f278bf2091bcb9c111e23b229f8da3f2c9014c4f3574d
- request
- 32f137490e393dd04ece3bf58c5e2d21e3fd8a23daf4bf4917d385a6aa30651b
- transaction
- 5c5f822996f6346fd0ec75ddeaa02c8e458ffc4f78781c2426d4de0380e49db2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41752
the chainentry 41752
- sealed to the entry before
- 4f5c6840136cb37f578b7314aa6969849e686b723ad782d64abfadd4ff7c975d
- this leaf
- 2c6c48e932b2c6832ae4cb3a32c19dc71597f10d42e7344d4e0ab886cf23d779
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- T4HJI9dMrArmZTy0/Eou0vGZaxR1aHXBb7Vnd2macqEeicpCzds/Itq21epzGErApMSa4PVkmDbw/5g87S+rDg==