why1 reason
spend_windowspend_window_exceeded
this would take GB36OH3UUUL72PQCQ466GGN7DMER3N4XJYC56CGZRS7YFIDMMYU2OVYC to 108 over the last 60000ms, above the 90 window cap, with 78 already spent
what it was decided fromfingerprints
- rule compiled from it
- b0d0748b08e706b2373fc0d0e6df0fcad61ba944e249ab98bdb2506a825b5cb4
- request
- 6a0099a2d17cdbedf36a88ddb7c310adfbafa64032ab4d7596904b30eee2ae4f
- transaction
- 2368d42f6b439f9653b209aa2f286a1351d2a39159286ac4214eb9064918f032computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65201
the chainentry 65201
- sealed to the entry before
- a4258b9b4ee204f0321df246f4f3a7ece6f60f4ad3b613ab5e7c50c555f076b9
- this leaf
- 4b033c1bf3676abec94ae2d78ffa961badad5fea5e1e13595e43c1d626a7b0d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bvBB7hrhA7KjanGolcjnW44tz8U8ghh5NLO3sr/dXe9dR7X0f7LZHcSUU0txSQU1i7zwi9RuIQqJTKeqoMJrAg==