why1 reason
spend_windowspend_window_exceeded
this would take GDMMHZ7IE4FVTWMF3BFZGK6HVZL4OT47ICFIKVEWGRYEETTPSBT5OUAQ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- fa8a0baceb4716a21af3e3d8ae1d815e8a7a18f6a376ef2f62bec92e9889ef06
- request
- 2e2e16052e7ef5347948400ccbad17e0b2050597a63c3fccebde6d009604d112
- transaction
- 2c8a323a6305ce4efb5818548cec5007e8080de3e9ccead78b5eef5b7153f405computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18087
the chainentry 18087
- sealed to the entry before
- 9c5f8a45e7a99e9fd8038f1c9ba6661d041f93f362e4b9957568bc78fd5f8b74
- this leaf
- 44c7116841d9e7613d4122148194c47677cfc8c2ab2ed24d44f5ef44cd1ace51
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DQqpB+6f1AfkzXe1iGcBqHMZNTE76/HtmUKZ06fL7pYewki9+rjTwRbRZf+qoCGs+yqCEHg2WPfUox8D7xTyCg==