why2 reasons
spend_windowspend_window_exceeded
this would take GD3WCTPVT7A3A7REH5E2DGM4VMTLR7LMDREFU7TYIKMDWKC5XXMQF5JP to 70 over the last 60000ms, above the 12 window cap, with 0 already spent
mandateamount_exceeds_cap
op 0 pays 70.0000000, cap is 40
what it was decided fromfingerprints
- rule compiled from it
- 246fea551e2d0e699ee11057b114f4fe12be53f2a4b2a4990642fc56ae52b584
- request
- 324ce83b0204990bab7016a159ac6de4c1f3b98c099eab240db8391f01b1e352
- transaction
- 1cb65776443c70873bed8ffb2693eb4e374704aec4212934c87ccec03dc9c953computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17062
the chainentry 17062
- sealed to the entry before
- 3d9d1a4335be4142dabb18cfbfc873163a327beb0a3e4ed739480a834e697a55
- this leaf
- 9cfd7fc8b258d90fc7b26bb26a9962aa098bf5c8e11d68a9fb5a72d8a07c0d58
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OuzReklUyhgmXaX6ph7LuNHYDQ8csbbhdcIOrIWu8MS5XUsInYq/4qYFEar+eaUSA9Ooj76zm2tROC3HSV3CAQ==