why1 reason
spend_windowspend_window_exceeded
this would take GD6VPQW6AZ5WSV4X62SN7YHXM3G7O66EYKHOXPCNQ6JQNS4DWN6RBSXI to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 682dfe81d88cca46936c58de0e84bdea2bd1e14e2429cda96b6587169c4404e4
- request
- d34954529e30a275c2839c539c74873fecd9ad93a92b35791fb5d531a42c4c3c
- transaction
- 9569889860c87b82dfd1ec8faddb02c4a7a611e089914f3268ad7d9c370ce503computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30690
the chainentry 30690
- sealed to the entry before
- 410da066d7031acc17a6811c1f3c8e5d93839ea6bd435e5e0e7c1d8697b324fa
- this leaf
- 6b252d46d7ecc5eaff918db8ad442d1e9bf9637ae120d12e213e3f7878080efc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1gegSkjxt+Hpb9m9LlqiQH0QdsctB0htWopGy7D2mx90qXx0rzeOAQIpJsLaFu9BwVgmHEebBZFlgZETz8XRDQ==