why2 reasons
mandatedestination_not_allowed
op 0 pays GA3LX2RTDWO2JYMIS2PZGVUISFDHRAEBYALSZVLNHFFFK63BRJPA43N2, which is not in the allowlist
counterpartycounterparty_denied
GA3LX2RTDWO2JYMIS2PZGVUISFDHRAEBYALSZVLNHFFFK63BRJPA43N2 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
- 3d27a1a1cbf4f6af9adfed768ad652fd4100c297c6afb257f2bd161e897871c3
- request
- 013dd31442b56c540c3d75493d15d019c33f02329c64e5c29775f0f1e7846c0e
- transaction
- e16ce72857e960b8db34af7d907c55991c7d2e21e14dcf1c4f771b0127432329computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73190
the chainentry 73190
- sealed to the entry before
- 5518ebb6000110ba4976dbec3334b87a371dff2508f7d9b1e0779c7533ef1e6c
- this leaf
- 2eb816f45271461c0826bae7624fd52564d79cb8ef78b0f092ab4e8cc9a53668
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9B/Cf3sBl5kyxYl9chJv77Baj8ymithwV8Bb3GN289dBtVEhvkWgGQny5XkQhwLX+XT39DzcIiI4LgUREP6hDQ==