why2 reasons
mandatedestination_not_allowed
op 0 pays GDUFRZ2ITDWAABG76NH7XQ4IQKTSG3LOVKHKHB6RTPJLK5HXAETOVMF3, which is not in the allowlist
counterpartycounterparty_denied
GDUFRZ2ITDWAABG76NH7XQ4IQKTSG3LOVKHKHB6RTPJLK5HXAETOVMF3 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
- cad637cf73ec503466cdce8207ea7d874eb6ed428bec9a18ae546299c5dad24e
- request
- 4fc3bf8eeae20fa00b2f769389de757b886d50d83316fba6dfbb85b7cfa086ce
- transaction
- 138395ab2f387a384c38905dab62af33131fb7ca3aa5221a739531a3e56fa3cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 322
the chainentry 322
- sealed to the entry before
- f0d07036fa95e38c405a7dfe52690d6a91600d99b5c9c8316bad58ad1e00f643
- this leaf
- d5b8b6324c5644585230e9d8526f5d45443447d2f2363f12c2ab9e4b8b4b1fb9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q4OzYR24rjRYcRX294PC5TEMjSn+iFKSWNs0ixRNwY08I8orwg1XfCygV2etGi3GSlkIpRUtFHjlt2MRjOomCA==