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: 5638762eec4aec21c06f49988adc77537169e47bd7abbea3cb1cfdd91f32cb7d
Tx prefix hash: f50f80c0c4d0438f8ea792c456f530a0559af7af7ef870c8cfe5b0a9f1eea90c
Tx public key: 6aedbb28d96b4b91f3b5f81281012433f02f5cf132ae79b16526cacac01ef2d0
| Timestamp: 1779631323 | Timestamp [UTC]: 2026-05-24 14:02:03 | Age [y:d:h:m:s]: 00:015:11:33:54 |
| Block: 905 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6981 | RingCT/type: yes/0 |
| Extra: 016aedbb28d96b4b91f3b5f81281012433f02f5cf132ae79b16526cacac01ef2d0020900000001ba6d17be00 | ||
1 output(s) for total of 35.123757889909 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6a15b8df34173300a8a64a9f41f805f60fefc740ebf73e100d3f5de5525ef940 | 35.123757889909 | 1039 of 0 | <b2> |
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": 965,
"vin": [ {
"gen": {
"height": 905
}
}
],
"vout": [ {
"amount": 35123757889909,
"target": {
"tagged_key": {
"key": "6a15b8df34173300a8a64a9f41f805f60fefc740ebf73e100d3f5de5525ef940",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 106, 237, 187, 40, 217, 107, 75, 145, 243, 181, 248, 18, 129, 1, 36, 51, 240, 47, 92, 241, 50, 174, 121, 177, 101, 38, 202, 202, 192, 30, 242, 208, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}