why1 reason
spend_windowspend_window_exceeded
this would take GDQJRIIAMPWNN7T44ZHKU57BKLCSHMSF4KGQEPASPV2TOXYIBND3FLCZ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- f188b67ec5b4fccfb36fcbe2bf5e1d65b05bde513e00a35245534c68226c7def
- request
- 3c6205e754f434b6a8bb1194a905bc4ffedf3284af9f6afc432276a77c4ef1ba
- transaction
- a8254f44cd37159fc55d432a7cf24bf97cb179b9b279f0c00201acc8c15f9a3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17428
the chainentry 17428
- sealed to the entry before
- ce63ef474632c53597c38da0de7a8ae8405b990bd7ee7368b6a93d46470b42c9
- this leaf
- b5459421dc7f9fa81b12641222c1c4ba8a6cbf0c08492dfea94f75fdeaae5ab4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NBNccOPZHVAvN4y1GwwsTWzNG9U8IktPsu8wBFHnYb3O/ivgbwx5oKTJIkOspZ3YwhkXuam2y4GvkKGHJQXZBQ==