why2 reasons
mandatedestination_not_allowed
op 0 pays GBTMSJRX2QROGXVCU3CHCFLKTNPXKUHC3E6MTEVE7CMBS5CWOAZQJCH3, which is not in the allowlist
counterpartycounterparty_denied
GBTMSJRX2QROGXVCU3CHCFLKTNPXKUHC3E6MTEVE7CMBS5CWOAZQJCH3 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
- dd9449ec8186593edb931877642e793e01696d97179483afc33740caca022c31
- request
- 691dc2e5b84adbc1f125f7d794575567bf8668f77cba2560fff6a6ca0b5e6315
- transaction
- 123b27ef61dadbfca286acb213801662673633949c2c7efb63d38e8c72c43095computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66471
the chainentry 66471
- sealed to the entry before
- c300fe9d06c8b6d62db961cd37cbd162be03511a491b65a6a26f0f98fe43cc6e
- this leaf
- 86031e5be3eb89a29d8fe1d73903a828992a33b575cdee86ba04d4b6632c9895
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tue5vcpwgUTcZVwyJVpimQBXNtqhZEWS2Qyp2A/BiHa4srfJftJm+7VDwoBXXphGeQ6woztK+2xFKPR7Z1MbBg==