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: 836873c97bcd4fd288d6c5e6ad508e25c1711082bd7754291c259dd72b94cace
Tx prefix hash: 8f3bea5763d8293d6802dddc89fb2a43093cbd605f2c8bbefd3edf860adce740
Tx public key: 4844a0c3b0f1432fa84cae010a8c3e61b4b747ee1e182b6e4fb9c0c1a09ddf8b
| Timestamp: 1779631143 | Timestamp [UTC]: 2026-05-24 13:59:03 | Age [y:d:h:m:s]: 00:015:13:51:55 |
| Block: 897 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7069 | RingCT/type: yes/0 |
| Extra: 014844a0c3b0f1432fa84cae010a8c3e61b4b747ee1e182b6e4fb9c0c1a09ddf8b020900000001ba6d17be00 | ||
1 output(s) for total of 35.124293840522 HMNY
| stealth address | amount | amount idx | tag |
| 00: 466c3cded088ddd6553125b5de2f8c5be0b6196893a2df40c0e2349270b0186b | 35.124293840522 | 1029 of 0 | <ba> |
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": 957,
"vin": [ {
"gen": {
"height": 897
}
}
],
"vout": [ {
"amount": 35124293840522,
"target": {
"tagged_key": {
"key": "466c3cded088ddd6553125b5de2f8c5be0b6196893a2df40c0e2349270b0186b",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 72, 68, 160, 195, 176, 241, 67, 47, 168, 76, 174, 1, 10, 140, 62, 97, 180, 183, 71, 238, 30, 24, 43, 110, 79, 185, 192, 193, 160, 157, 223, 139, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}