For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 476e60259aeec6ad731295df5b772b2863de96ddab73e6b5403a7ab34ba3280a
Tx prefix hash: d6474fc72fe0fb55213450b2b844cd0a27e9ac54383026ae771a8ef46e1f5e99
Tx public key: fdbb32fac0230af8dbae05ef7a2a497e244bdbc45736a49a72273d9d14b856a2
| Timestamp: 1780399247 | Timestamp [UTC]: 2026-06-02 11:20:47 | Age [y:d:h:m:s]: 00:006:15:29:01 |
| Block: 5270 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2650 | RingCT/type: yes/0 |
| Extra: 01fdbb32fac0230af8dbae05ef7a2a497e244bdbc45736a49a72273d9d14b856a202090000000126697be300 | ||
1 output(s) for total of 34.832546004569 HMNY
| stealth address | amount | amount idx | tag |
| 00: 14b441a0d2265b02ef5fdae55fe441f2b7dac79157724db2c2a9b33e1a0c702c | 34.832546004569 | 6679 of 0 | <f7> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 5330,
"vin": [ {
"gen": {
"height": 5270
}
}
],
"vout": [ {
"amount": 34832546004569,
"target": {
"tagged_key": {
"key": "14b441a0d2265b02ef5fdae55fe441f2b7dac79157724db2c2a9b33e1a0c702c",
"view_tag": "f7"
}
}
}
],
"extra": [ 1, 253, 187, 50, 250, 192, 35, 10, 248, 219, 174, 5, 239, 122, 42, 73, 126, 36, 75, 219, 196, 87, 54, 164, 154, 114, 39, 61, 157, 20, 184, 86, 162, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}