why2 reasons
mandatedestination_not_allowed
op 0 pays GDQK3DMR2N5QZIGOQRP7FJBERHHVSUHNZR3KTHNW7EBL5YFBIB5GOZQT, which is not in the allowlist
counterpartycounterparty_denied
GDQK3DMR2N5QZIGOQRP7FJBERHHVSUHNZR3KTHNW7EBL5YFBIB5GOZQT 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
- 0ed7b89a8bdcbc4ea70a74b342b787994f170e78b8de4e2910b882fc4686aa15
- request
- 4863657783f23064372aadaa5046e9a0d99b14a591cba958f91dba4bd7c465c6
- transaction
- c48329d1af2b2cba3263b0a788c221f8a1cba36c5eb9d0ba528939c6bc11841ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1331
the chainentry 1331
- sealed to the entry before
- f3bc905c1c3580d38a5aca6f8e3855dc021cddc2dc23e3200358fcdb0fa2d82e
- this leaf
- 74f25d55105d03f0ab420d06a6b9838ac9f8ae175a0921d0c1c983cf96693236
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sLFmttfEg60zaelLF42cTbNaul9/VVWuZOaFQDEvAR8jhtlERq7vcZiBeu6EiWWRJDPUc6pQuhxu3k3Q5YMIBw==