why2 reasons
mandatedestination_not_allowed
op 0 pays GDYFBXEHBNQZHPLZ7CF4V34AEJWNM6HMREPCKCU4F23ZSOZSIGS7AA3Z, which is not in the allowlist
counterpartycounterparty_denied
GDYFBXEHBNQZHPLZ7CF4V34AEJWNM6HMREPCKCU4F23ZSOZSIGS7AA3Z 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
- 2c3965fd5b0e59519cef94914dde4671892f4261e79198165ef33cdeeb838f98
- request
- dffe41296cb6784f733b14a319c9faa4d107b274bf9074e11687d77a8cdb7e0e
- transaction
- 308c32a31eeb480aff68d5f6eaf78579766815ad68d8e1920b92634ec6df359dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17928
the chainentry 17928
- sealed to the entry before
- d031c82ff55a282469b2b33293c71b5dad2aa2deee9e1e35c9803aaa0e42b76e
- this leaf
- 66ff62dd7983ae5eac63c68e77b0f4ae46ab59288794a0d6e0a2ece4e2d0537b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- abUx5u+LW51HmbkfgmuTwvcV9K7yu6rISi7Kzzj19Fy0Amx5B0YnNrIw/Gsh3M3u+4pmR3h8nXs1oh+Di5MXCA==