why2 reasons
mandatedestination_not_allowed
op 0 pays GAAGN3LYRWXKRHRDQGTFPYT4YLXBFFF6P6JDS7WLVAI7OUJTAXF7VI3H, which is not in the allowlist
counterpartycounterparty_denied
GAAGN3LYRWXKRHRDQGTFPYT4YLXBFFF6P6JDS7WLVAI7OUJTAXF7VI3H 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
- 0e8cb88dc6e9ce1e662aa032ff48c427a99f8f42a38826fc14751044c8d96011
- request
- c48c882244cebe5dc624370c4ec66a013bc4e43eeeef13b653b58afcaeb4ee8e
- transaction
- 2a7552ee91966d0c8f71d527be2fa3457e34340e75822306447874a1714ebd38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16104
the chainentry 16104
- sealed to the entry before
- a6e5fbc08000ebd5e5a96561de23f85a5236f7a29f5c9413fbad84f0d38bfb46
- this leaf
- 1105baa95827939097e235784345126e4999a9e79e3f69b04cb9e2555a049189
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QAw1x6NFo80uXlZK3O5wmDmneXyL0XmfgFSF5G1XannC8YSShIEUZmdvkwE7nJPLNgB3hYi0hKR8ktoMui91BA==