why1 reason
spend_windowspend_window_exceeded
this would take GDATSJP722LBBQTS7OJ3FVUK7UHEQUU3OD5VGAAKXKGQDOXECEABTY75 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- bdc8e88034dbc504bdc81b63cc1261b96222feeb23a53396909277548d566704
- request
- 1df7d5dcc315dc72b385cd439c99818745c50c8048cf6b1356bb908bedd7a7eb
- transaction
- 7d8dbe9c6436a0e53cc820909d5606271744a8f45dbb7f2c8a70bc3ec7646baecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67850
the chainentry 67850
- sealed to the entry before
- 0456e0aebb8affda28bdf7f8df8a03d7212a77bff40036b67d5cd21318f3c384
- this leaf
- ecd0c73d3233d8b3e8d4d996d22ae82e8f298f13f529725712eff153c3157ea3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rXykWBqzhCuPtEFcbuDPt7bcfq6w1tzoE89w8m6TngBg30E+uUF6LlNvEkBeczwv96i7F0RGarpZIWex3FYpBw==