why2 reasons
mandatedestination_not_allowed
op 0 pays GDLUSIMZV2SMLSZRIZR2XYRFAEEOPA6HAJBVRYGHGM4NFMO57ZZJRLAX, which is not in the allowlist
counterpartycounterparty_denied
GDLUSIMZV2SMLSZRIZR2XYRFAEEOPA6HAJBVRYGHGM4NFMO57ZZJRLAX 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
- 54d60aeba8469fdfa0cefb9f97191380fb8224fbda7f8b1a6b16dba74e42cd28
- request
- ba291bc88efaa7683359a85e37f5963eec64f1958c36ef597ed25eb0ec8a0acd
- transaction
- 346158e965317c5871f665380634cdbfb9e76870f00fbf8843b729ba8fbf9615computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 632
the chainentry 632
- sealed to the entry before
- 224c87d9c43505837fd0fd6da7cbb1bc750a6e14ccc79a2ddbb69f0bc635981b
- this leaf
- 0fad82459bf39051547fd7493aa7dce1fcc79679d445b6a436a907e9dce9c420
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wlKfo/QaTt9+avAnm9z0LU9BcvGs5e0mgv3c7i8NMrxfsWqMgPRkH+K4cVp8bQYsayGJy017/hCOHMoUT9lzAw==