why2 reasons
mandatedestination_not_allowed
op 0 pays GDIMDTDOECBQG5VQD3WECUH62OWN2OPJ3HFTZEAHSCBF5JLV45SOFZGZ, which is not in the allowlist
counterpartycounterparty_denied
GDIMDTDOECBQG5VQD3WECUH62OWN2OPJ3HFTZEAHSCBF5JLV45SOFZGZ 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
- 03985873d7de2d524f4c059a722391dbe14067284d96e54825d96deced6a64b2
- request
- 076f2ae3c52dae5b871e1041b1656802f7f861d532073bc512c0ebb728de4780
- transaction
- d1062a8d757d519e4ba08ed8df313620ccbb63e8af347bf941f2c4d9aeb2abfdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5146
the chainentry 5146
- sealed to the entry before
- f262fde78b28d6b35148f89c2c38f1220b643f166d1a8b3326b18c5e45a11a9e
- this leaf
- 0654702daa0fb3f10e6b2b7d8791e746bddc39076d9c49d558c3eac0bd7fb2c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8UWa3aWIVY39llooPjBUKOM+DX1UJS+dc0/4QvtmU2B08sNHX2oat3tpQ4Zrxa0YKIqAn5ThgH/bqZKcL5bDCg==