why1 reason
spend_windowspend_window_exceeded
this would take GD4HOB3DPQDI3ZWSHZVKBNLJHFUFANQYJEQ3MYCJ7OOEQDG4J3TY7ACL to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- ceba4e2955dcf2d2631f9c6f5ef1477635f88ea08961f009bccc0cecd5a5cac2
- request
- e6ec916669e272b77319e3d2be6bd4d49c0106141c8814be29164cc9cebb58ac
- transaction
- 26b83b4443f1949a909207d5e913df4acab20b4406dc61d15ae951fd6f777e6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34802
the chainentry 34802
- sealed to the entry before
- a33151af80cfcb92e4d719b060d7cafc0515d721be22eca8f2b6e485b78484e4
- this leaf
- c9d138dfd25903eafa8b0c2648a533c36d1c69eeac20ae5d44e34888ac3c0d7c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- reR1eTU1pHd133DNl/uLaCBjSbANg9gg109YoBhB4GZ5u2g3EmAeJ17uQHftjdVqAXEpTeS5+0z7GzlWn0oeBw==