why1 reason
spend_windowspend_window_exceeded
this would take GDG7PFE6QXKCU5K4ZP75LUEMR56B5D52E6T3QUERUFHLBWSTHVDWII3O to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- a216372904fad11f259f5246503d1ce06ba80a865a969757af1c336407a2eb67
- request
- ef8071ac0e9885b5737def548b97971f513b9a6a6af3e5be48e7d96bde64d72d
- transaction
- fba11eb952e31735d444cc5a3b1f7247302fd35fb90959e07e8e583280319fa1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72082
the chainentry 72082
- sealed to the entry before
- 14ce45202b41d4628cb2cb87a2ed9bbcfe10f4db3ec4df5d127f7c5a3dd67dbe
- this leaf
- 6f59dc3049d5323163371b9506875ccfdec84693d317bb5ea776b3650aa9a771
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MW27M3VJYCOZZA54/nMSbLMNFfYql8uUqoQEzhLUnYKYn3xpjkHNaYgwxN+oCdnoGTGJy/QdttV3WNSyoAo3Dw==