why2 reasons
mandatedestination_not_allowed
op 0 pays GCQWVE6Z3E7NXQ2EACO5EVE7BDJY2BUOEFBA2PDT2HB2RX33URDANLE4, which is not in the allowlist
counterpartycounterparty_denied
GCQWVE6Z3E7NXQ2EACO5EVE7BDJY2BUOEFBA2PDT2HB2RX33URDANLE4 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
- 0a1eda7861ae4427a9344dd5cf009434ebd167994589749f39d52a0b02b37028
- request
- 97384ea3004c9acdfbfca1dc90bc1dab5fd316d295e08348fd31998e4c6a379e
- transaction
- e32468772eea1b56d14ac67a6d65e1d7e6316fb819d09f6bd2f5870589d848d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22900
the chainentry 22900
- sealed to the entry before
- 37b87a2480374ae2fd893e8688d58e6ba9a0a857251c098da715c63ab3f8402a
- this leaf
- 761b33fce01851480de02523685810d35c8fc8d1c9f02cc675b139db175302c2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MZ04Cj6g8QmoMMReeUI1hr7T7U1Lc3dB5+VtMMPnlZuTo9AMYp+UzMosvUs4E0I4tQ0EbgZ9WNK+UPvm9rSuDQ==