why2 reasons
mandatedestination_not_allowed
op 0 pays GDWJ5XQ27FL3NORNMFVDB7DWU3ERCYXKEIMQPPPUIXMDVYNXCOV3OEKE, which is not in the allowlist
counterpartycounterparty_denied
GDWJ5XQ27FL3NORNMFVDB7DWU3ERCYXKEIMQPPPUIXMDVYNXCOV3OEKE 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
- f4a3c1e0819c6897e552240496b0b33ad7ee568acc717df10cba0a53ea3b4891
- request
- c2cb06a3d719e5d2ebf013c2fc6e9e93f1351fd06202419f9d42848cd6ba5bbe
- transaction
- 0ed70c20f009ac0e676a86fd8c0ad66ef6e506f877e4bfb1fb8d781dd2e28bf1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68154
the chainentry 68154
- sealed to the entry before
- 455c91c10464d6fd53b84f3f1ec828d1584af38b50d82cef33a7f69b64506a1a
- this leaf
- 2e91c17470044348b321745fe7577e8da3861987eee55d9e94279aac048570fd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ThX9trgaglIBR/DwSGMty3I0vF1fPX4rORS4PSSuR22H8KQis48vwIu0/DGq9hUdRW111E8DIWjcunK6svjuDQ==