why2 reasons
mandatedestination_not_allowed
op 0 pays GCV3JIKR4NFLPLIIHZNG6R4HOPX52GBPFVTGO7OITOUBFOPMF2FZ6J3E, which is not in the allowlist
counterpartycounterparty_denied
GCV3JIKR4NFLPLIIHZNG6R4HOPX52GBPFVTGO7OITOUBFOPMF2FZ6J3E 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
- 8d630a17b4858332c76490437b7302b04a3a1d4c917c5b471c879da78f7a65e5
- request
- 30e6745cade741f88052013d453da8c1a4b02392986b6d4533d73ba5f8c74f93
- transaction
- 11a278a36ca4b2da7f678e1125fc34110be903212d39fe14770945616ff9dd26computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69443
the chainentry 69443
- sealed to the entry before
- dc23e250c05778e9e32b0e230ce93d93313f990050206c30dbc12ebb37e73bf7
- this leaf
- 80628f42d1543efec12e0a7c670f2757c495a75c5a0b107fb6c86c6227859a1c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WPtVcIFzSwjrUhWKm71qPHa8cl0CDULLOQFZvKEffdpKZTUSzduajtoEQQfaL6Sqhjh+N1hHjWrxMDpz172oCQ==