why2 reasons
mandatedestination_not_allowed
op 0 pays GDUDWSEYBJ3B5O5RAP3OWKF52OOIGNHHGWRRJRHZYYALY5V4HMDK5OGS, which is not in the allowlist
counterpartycounterparty_denied
GDUDWSEYBJ3B5O5RAP3OWKF52OOIGNHHGWRRJRHZYYALY5V4HMDK5OGS 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
- 0e5ca506f6b1c65913fb02bcb667cb5a50837210216a2c6f1458e8941018dac9
- request
- 2d088bac445412468154d9b25699c5101b4ffa82bf6b382b9a2d4681da353390
- transaction
- e1226dc2ed09eb08b93a8ea756110a0b81ca861e8861cb77239637c13e9b2377computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45688
the chainentry 45688
- sealed to the entry before
- d219735b90465b7248e13f9f6fa9eee75391e240e046dfcd9b5701d6f7236b82
- this leaf
- 6511f559e769f9a5d916a36dddcf48f00a835daa4c81d37a40b999200e66cefa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qSGUB40OvDRiTfS+x3thCTAPa3zzb0tZRDUbYjXjJDx58/qOff4eQy8fFacuCrd84PmN7Ud2e9VRPrO3+Z7yBw==