why2 reasons
mandatedestination_not_allowed
op 0 pays GD2P7J5XFUCZ4VXPG3CZZMHJFYXF7SXD2QSWWKTQVHNBAPUOCRDYXDLU, which is not in the allowlist
counterpartycounterparty_denied
GD2P7J5XFUCZ4VXPG3CZZMHJFYXF7SXD2QSWWKTQVHNBAPUOCRDYXDLU 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
- dccea4038882e78502d852a7dfa9ef5ef7913839649d86cb8a912307fbf510aa
- request
- 2d8d8056fffa97eb32c534a21249df0d782e414dbffe7453d2084a74ad1fc4da
- transaction
- 90d49633385e62652c31f5ce4567680a79e798bdaf3315812e7cb86736c626bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2036
the chainentry 2036
- sealed to the entry before
- fb845e58aec144fa27c0dcfd8527000147c995edec04c213e3f8bc940d281ebd
- this leaf
- 203567f83b998c4b35e55eb75bd414797fb9029b0ced70cc56b684f4708b0922
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d1PecwHHh+5gruARhe8sAi5UNAS+ZPbROBGXCrQlOEbFz82Jd6S6JtNZW0yiT6kEtRrPhs4P4SeH8ImNO2lYDg==