why1 reason
spend_windowspend_window_exceeded
this would take GCD67NHC3SFRF7R64HDYMZO7IZAMWAQLGG6S26AQSBJKOMZU4HRX2OQJ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 3f69212ac8e09b04a6eea3feaf4343b92907dc3309ecc2c21718bb07cb4c566a
- request
- 5792e6c6661381be09d5bddeb97460373d8ef08413cd0aec206594503cbe61da
- transaction
- a5832c64af46157972bf75c9c24031b4dda3b9f2573801ac2d83ada8aee04d19computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65100
the chainentry 65100
- sealed to the entry before
- 600e5a4fc6e29f7454fab2c028d454e850dd9e5a7fcc36ae7888511e73af997d
- this leaf
- 047079734aa08c1936e2c491c5f2856d44719cdfa674248852ba7167f8f61867
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iIh7O0aNJ5sAYgmj6UvA2Ef6we06GKOEHQjao30yr8qkizTEqS0xz/g4gd2V4cvfI1siWTVfEmyLwdCDhbtMAQ==