why1 reason
spend_windowspend_window_exceeded
this would take GAIRQCZCGRLKNBLR6JCTDKOHB6UPVCCIN5I4KYTPWZTCPKAMHVEOFMIO to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 0ee1573a1a3b162305fe37a081adc4e9f818f5edab31387428403ecd4f7cf09f
- request
- 9e12fa61bcbb4e3e7ec89bf727d982a4d892491a281aee6fa05df3fe0d605ba7
- transaction
- aa25e64e8e0f331250cd699bd7f37effe711f481e89d0c30afe15529a546940bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66574
the chainentry 66574
- sealed to the entry before
- c96a6511ac8bf9388db142094f08cacf8780f9eb0f05a1029f8c865fb908ec18
- this leaf
- 137bfbbd207984a43ea54f9fbddb2b2e7320ea40484ab8f4c30a9a8f6459b208
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kdxxAeQ5uY6n6IwyUCUH7S9oxowvzcdVhSj0VAc29aifHb4+IGDDTmGexQvtsZv82JNC8S9ery4FMYQ9YhHfAA==