why1 reason
spend_windowspend_window_exceeded
this would take GD5JZZAHW7ZI5OAHZX3WAELBEA75R6V2UVZ7QDIZSXJREDS2GOXGZOQJ to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- 27fbaa8182790b6b00ceff0eaa4359ec6583d484b5c629096e9b3b0cbfe10eef
- request
- e81961c9abab9a34c20066121f6b74e9a5b2577c4f8f0e153aff3c12a73f34d0
- transaction
- 39370edff31f74f2f69c5f07eb9d8e7de4c8d8a4571efde570ddcebbb564f35ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3700
the chainentry 3700
- sealed to the entry before
- 2cae254dc37becf7e1088954914a6abc7a64dcd76f59877c0eef5ceed0ad3808
- this leaf
- c77447bd8f2b4a668ca9a67d1211e37be82f8898783cfaab5307ce90355cc319
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xo5h/o/ko576wHxWifRhWySeoz0Eml8QlGpRNOoxTbjmUzyepqWMUyYN6gTo4fWLYx73HxdmzgQiGDGSDk5vDQ==