why1 reason
spend_windowspend_window_exceeded
this would take GD4236BFEVFH6H6EOHAZGBTCO4IX25V6V3Y2UTXBX52JIO7EFJ6N2OQS to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 26588eea8d349b3dcf795f4d641e267fd77e1a0f8b382c1ffd2d5a4d8c0735d1
- request
- ec0592dd95acbdad86df8ad9b7f39408607fa322a3eb00d743d319d0e50ced8b
- transaction
- 3566ddc7170a68b51d69765d6f5ba73d43902982e7439becd1e942bbca20a974computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76802
the chainentry 76802
- sealed to the entry before
- c3843933c18d50c7d4e44471b91ed8d0b7e9c455c459c227c1743aff8a6b66ea
- this leaf
- 3b2b33f053109ce7eaf276e0863f246a19f0df08a7b6422035878ffeea3f89dc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m+sYc4b76YiMRm1MQ0BGjGXI3B+o4e4+fjsXuR4z9VUOk72ocASxv4Pj6m1QlnXmL1TpNFnxP2luUetBNMjWDQ==