why1 reason
spend_windowspend_window_exceeded
this would take GBPGZZVFOBNMZW7AEKTTLFCQ2DTHEVTJWNGRUGVM5SORYH6WNHO75TZG to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 89034ba69cdff73dccaccdc2aaef7279ca18c7c7344e22e24696dbff6574b6ad
- request
- 3dc803a086c54ce8c4cbd916514b36f91075d5c81b487a440fc934df8be6018b
- transaction
- 1ad5b773f6b69e60791028dc19db64df9ef0c6657a606266f648e3c5a7e9a559computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43039
the chainentry 43039
- sealed to the entry before
- c4b8e2d90f1480a0bfeb52e7f24d16d3bbada7abf7828ca57e8c671ff53cd28a
- this leaf
- 079b18023064352fad7b3822eee98eca0b61c37bac9bf88e410615ec52e48ff1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 24ZtdJypGlTpxVtnLKGnkq2a3zyhNaS3Bgu+mGz5KG/HQ8NxQXPlTdXiX8CEveYRtfvzGvwHQq7zTwAyJUCEAw==