why1 reason
spend_windowspend_window_exceeded
this would take GCYMEYRXSZCFQ4IGRSSDGUV3MSSSU7QXE6UGGDFKLF66CWAE4DLRIAHQ to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 534fceebccccff72b3bf6474baa22515ceee9c55a83e79f5f128479a7a2c85f7
- request
- 6962e4dc6b386f58a9d16d3f1fa41f31c2fd26305fcb98c940ca7114f3878e87
- transaction
- f86cca216b9a9cdf58374d78ec1e6098cfdc25cb6cd1eadeb6c5cbdcb0ec08ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18280
the chainentry 18280
- sealed to the entry before
- 907af85e5243a9d49ca3a4685dcfc205672267e0b771bf884bcbc11586c417f5
- this leaf
- eab7c587c63d0eb2253a3034a9fb0aac4e15281baa44d63d17ba5127d96ec206
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- i7gv4jWua97MgrHkumTgRgemKknRo5sFdhTsktMCZgFc6ZDkj6PGMgIP98mIPlZkwN1tAl+IIbHS3wDWm1h8AQ==