why1 reason
spend_windowspend_window_exceeded
this would take GDXTPGTLHENNT5CLB4CPQ2K33OXRW5NOGXSZ3PUFNAZKORJEVULC3SZ3 to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- f70a42e36130425a1bfd07d4ed191ac53d72e47e9209cb12985b1853121069e3
- request
- a4f706c44168e54c388792cf69490bf79513b792da768a0a5edb85c6fb91255f
- transaction
- ba341b8746a63465a6bd2801d4ccc68faa31e082450fc0f89e151dde9a90102fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76657
the chainentry 76657
- sealed to the entry before
- 65892aa3c80ba37a20578145a3a8d38a4217d08287cf94b0331459940cd8c667
- this leaf
- da3c4cad058fdcf15fcf246f77d77bc6b9c1083a680aec0990ea5c6e218bc8c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9ulcM9B9g7guyGOqf+DEBFD1GnT+CsJg96dS3lVab/BLKMTCRqUHZcxBKwHOVZAEQfKq9F9MpD1R0OgqyHjBAA==