why1 reason
spend_windowspend_window_exceeded
this would take GAR3KH3UXCCONT7RC673ZDP2CNJ5I7WOGCEQHJH6QN7S52JDUNUOMTKH to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 856bbdefe7643b0af4cba0a40e1067adb84fa643a3e0dce17b33af6f85f33842
- request
- 746275ca80be6acb19d92fd554a84148034a2b283c38ede9b66e86ac5269ddd2
- transaction
- 64e7e005aab6f60587bf9380db828af3577f73460a639cf8c54a4abb713d18a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3695
the chainentry 3695
- sealed to the entry before
- 07d976cfa347b51564147f7400b19ff948d50458c37977604f1ed34f93f3534e
- this leaf
- 6468cc9996a8ae8bf5ac64e71954d72581ffeeb1718fd6406d838737ecc3141a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2QP8jTBmLxtYSGNo69ggAB8DswBAKjTOuC04Sb6MA8M43mn5U2vysQ16ugMggbpnGrrKBsu58eZqxQjTp6VwBw==