why1 reason
spend_windowspend_window_exceeded
this would take GDSXRJCTN75TRDFME6DBOEEQ3U5TWOZJXWOGBTU6IQBLFGVIKMS66FPN to 30 over the last 60000ms, above the 12 window cap, with 0 already spent
what it was decided fromfingerprints
- rule compiled from it
- 52e4f21d917aa5497c41bc19ece3e73a291d49dad949a125c7443bf13265102e
- request
- 5328ceec5f570ca150b0649b29a06bf59d1539a218251730e80f374ac605afd3
- transaction
- db1cd648a965a874348c03220079429fa5a2cd45d729677e1972e9c5ee389732computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54483
the chainentry 54483
- sealed to the entry before
- e2a05d4015be60ddecb5c6f3bdf44aae593022b9905c17a68ed3b8b8ffeb086b
- this leaf
- 727ac9f9a04d1b1c1c7b8a6d2abb7f0762e9c18afab5d9bf051fe5bf40449675
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PhdTUffrpupyvE7speHEwpN2M1Qwix8XRUN0IpzrXZrvikBBy0BmiVHRe6Afvk3p8WG7rJCLaYhi+BSrdGKnCw==