why1 reason
spend_windowspend_window_exceeded
this would take GBPNILDYFHXAEKTK2U5SVSREEKDB3QSRG7QYJKCUPSGNRBANVDDJTGMW to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 7cee5adc876f58826af3fb0a5194f7ba96cc474b22b11c24ba6b90a2221c19b8
- request
- ffe29492e6a181b707aa59c45059686cb9a0fd8eea56470c04715105688e1d74
- transaction
- 7b13d5619789df20dfaeff1cfdd7f4b59ab626315690a537c9c2d531fed16f2ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54201
the chainentry 54201
- sealed to the entry before
- c0c4a2d3fecd1bd01bfcc221e0140236172759ef42e389500a6c461033d1d33d
- this leaf
- b1c04a1163449bf27be7ae07a536a1f6ed83648f4d78743c85453ed9e1211c6b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PZB7FePgAsdXzrNg8HioVJ1fZxq8IrsuYfiUhipbuTM4mlH4Hby+/5nCtwM2GUaSuzarPTyYHkKCEwVQwFIiAQ==