why2 reasons
spend_windowspend_window_exceeded
this would take GBX6YZFU7RRVY42UWFRY7LQXQJSBKN7CKDIDBCOBWIU3VHXS34IKMTBU 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
- 2afbdedb33c36f9c7fbefe9148557edb2341f3a963606bf133d0f7f7bbd0aa9c
- request
- 2a414b464084e98c6b3752a2bd969273cd138b3046097349269bad5906c6b6ce
- transaction
- 70b3988ad958d0fe5e461c33f9862cb65c986cf7fad2e4ebfb6edcdf2dd40e55computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39129
the chainentry 39129
- sealed to the entry before
- 5015627f35c06efe1f53ebfe27bf7acad9be393a2b6eb3fee2adba51fbe432fc
- this leaf
- 516cca8f23d0abc23e8c5ae7cc9b8de7bea1b223509a40331ef4e5be0cbcbd7b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2LXSeomIzVeO0j3zGQZOx5Ix5MnMi/733x65SDsENr49/EEbVz7K7a0FZ6Ciu3YE9IFaxip9+B6v0IfdPKFNAA==