why2 reasons
mandatedestination_not_allowed
op 0 pays GDV4R4ZL6EZL5GRBNFUP4B2K4MHI7N2S63O72VYBBBFW2WYKEZ4JKF4Z, which is not in the allowlist
counterpartycounterparty_denied
GDV4R4ZL6EZL5GRBNFUP4B2K4MHI7N2S63O72VYBBBFW2WYKEZ4JKF4Z 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
- 6f28cddaf65cf30fe1a4bcace593e4f557fa7cc214e7b28bbd3df790d604063b
- request
- 3fd6ffd44ee57ddbb85155ba40ada1b4f286d5cbb1f6fce8db98efcceff804c1
- transaction
- 3e675bc7ea4f2955c3fa8a2a332cf7a632ed459391fa7829d7dcf3401d6fd5b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51552
the chainentry 51552
- sealed to the entry before
- cf10328eeccc56a8a5d07a0346d299b62d82d1cf58f931668aa9248b83e96f82
- this leaf
- db77932e989ca89f5c95cc6bf5dbfd7584d74110097729b0488f826eeeb0937f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qBr0aJo/u7YZHZkPV8s/6hMdD8H49M3QXhYjZ/8nRs6FIlUhzlygQRerShmGWBtQGhSukITZA7zracI21swbCQ==