why1 reason
spend_windowspend_window_exceeded
this would take GCJDYDIGGESV5EML5VYC7GZEGYP63DHTVH2QE2VJXWPRHKHCGBIGWUEJ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 87a4728e7d4f82ba6de6b2e99057c29b45f033e037dcb022a7e6d13aedb03979
- request
- 0a51535105a438f6b56fee1cc7a99443fc9fa709866bfd7dc77578ed3cf3c816
- transaction
- 545af0675d0fce314db4c04f6ef38831ee28da712ece1f914c5d5073b7c0032bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5431
the chainentry 5431
- sealed to the entry before
- f1394811d81e5f58b09c9511b7881bcf4471af94fdcab3262cdf9fd072ac6ccb
- this leaf
- c886719b4d0b38734f41e6d5601c4043147077c051bf6b285003c3539815f8f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Npm6FIsaaBOJ/5ns4kebU2pjlHncU8j17Xg7ixs3TRIal669DsUtzDPr6buN0I6cgfHtK9Z862majc6i97+SAQ==