why1 reason
spend_windowspend_window_exceeded
this would take GCXRDLLLR3EQAXV54VNCM4JAHNIARFNNBQ3FTHAPNH6UDX5Y44QBCHBY to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 370cd384d74d63a18caf3c7a6ee2d1179f18cdb3cb53a16daaeda732c5657a71
- request
- 0369f194b30ac5f76afa14af8459cd164a0f5b72522d770ec17be1022ae4f647
- transaction
- 064a60230b066ea1f58e68b06534e26fe5c1ec6bc44df5d5942815a19656b660computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17685
the chainentry 17685
- sealed to the entry before
- cfa4a5bd4403d398ee217891290c2c30374e3e417e5f4aa4d220c5f93d010c80
- this leaf
- 59ff1f9062aab30e09830fb8e7bd5dcf0b000f65381916e5de5668d1b486a8fa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- suyonp7FstYtebP+AR7WiuM9trhyu3aCJihcoVVjRUsD78JvA+bW1XNlGqlj5DHVl9EP6szPHRS2mMEUSkG8Bw==