why2 reasons
mandatedestination_not_allowed
op 0 pays GDTQ5HTRKBTS7DWUBFSAGRGUPHS4R6446PXSDVLL7XUAC2UJT6WI2BL2, which is not in the allowlist
counterpartycounterparty_denied
GDTQ5HTRKBTS7DWUBFSAGRGUPHS4R6446PXSDVLL7XUAC2UJT6WI2BL2 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
- ffc9e7e5e6bf3765bba396dc9714b2caf88fecb7893f0095e889d9497c25f95b
- request
- 95099d65b4e8c262666d77a5f18436cd03b4669e080543449f0ac59146f67bfd
- transaction
- 1cfe7a421983d8382946fe539cf4097ef21282ff93e448cb98324b22bb98b9e5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7213
the chainentry 7213
- sealed to the entry before
- 00eeab547877e153d8ebc20251e1cfbd137f4e66a1bb221e2f5b6d078326d7c3
- this leaf
- 9d4b545ab30be7f708c19dc3108986d61e497479793a2b7578b026887cd0d831
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 57l8gMRy0e2pUhayzlVarInwhJadaHfx5BLDicLBsUn8x23GTOJRa4bUTiwFy0TTTh7gAbBewoJQ1ZJlLAJ1DQ==