why2 reasons
mandatedestination_not_allowed
op 0 pays GDC5ZUQVRRZFAVMECD3FWH53I6FTLFPLRRAXHCQBWCDRTOJA6HM4G5WE, which is not in the allowlist
counterpartycounterparty_denied
GDC5ZUQVRRZFAVMECD3FWH53I6FTLFPLRRAXHCQBWCDRTOJA6HM4G5WE 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
- 990a882d585baf778d63e5e5e6c1c4a64eb1c9c531bd0165ec0fc87dc66c5bf8
- request
- 46c60afad3d0c24aa48e0fe0dd5d5813a270a19d9addfd3b44a715814bdbfe0b
- transaction
- df0e4e83ad7abc3ae9597c23283dc8c03a50dae9c4fed4f2a9cf5a9d9dc16e7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33548
the chainentry 33548
- sealed to the entry before
- 7594773e03e5f0e5bb2b2f732c2c1307633dae42aab890d044441e28b20f2351
- this leaf
- cf1e36087b7851f1f79867ec10d7d570d96ff0efddf95e871d6639a2b4c14988
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GG5Phjpa2W5kAyTcz5GL5eR1Mg6XbQPk8G0073pEYGSulkuKX5RRq849ckBP0XKDbhMS11Oqlyi3evz6DkuVDQ==