why2 reasons
spend_windowspend_window_exceeded
this would take GD5CBXJCFRJI2Z7JYE7AX2YBFEAVN3G6BG4AATAA3JMA4BNO2W4FNZK5 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
- a4613291155dfdd0b3b809e89964715e9806e35df610f409850171f0da59f170
- request
- b5f0a751a0051f0c0796d9f7e906d46173e381e20dbb3545cba7d480eb68ae39
- transaction
- 4d6b940fc35f12909763c1345e3890f9b4efe982e9300869b6edf147c0d596a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40836
the chainentry 40836
- sealed to the entry before
- f3a0721e21a4132944c29192becff825e19afae9079f2818c5ec9b0149a4858a
- this leaf
- daf60e279643c6450993499c88267d5611d244c0d42d9bbf87f26163e37e24a4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FIt7+VD3whKzygiq4N34XvDT+3X3+yIVIL1DVy5a0RQ0UZu5I+wnPsb1IqcxmlOhg7TRZJKEqJdy2tjE587sDg==