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: f792fc801e3ea4e71e5311ce177d6160b92b8b84fae2db5695959626ea742da9
Tx prefix hash: b1f03e4b49cc77372630dfb4da0849e3a1b9e56c0315dd730c7fa7c4117236ed
Tx public key: c012a6e6abffdadbd1bbcc4063446277aac537d4c88eb98e288853001ab01d47
| Timestamp: 1780713032 | Timestamp [UTC]: 2026-06-06 02:30:32 | Age [y:d:h:m:s]: 00:007:08:31:44 |
| Block: 6169 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2576 | RingCT/type: yes/0 |
| Extra: 01c012a6e6abffdadbd1bbcc4063446277aac537d4c88eb98e288853001ab01d47020900000002e49593ff00 | ||
1 output(s) for total of 34.772869535800 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4636d6715472fe33ef4b12fa6a3ed1e1002ba3466d0482e5d156cd9509115f59 | 34.772869535800 | 7646 of 0 | <02> |
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": 6229,
"vin": [ {
"gen": {
"height": 6169
}
}
],
"vout": [ {
"amount": 34772869535800,
"target": {
"tagged_key": {
"key": "4636d6715472fe33ef4b12fa6a3ed1e1002ba3466d0482e5d156cd9509115f59",
"view_tag": "02"
}
}
}
],
"extra": [ 1, 192, 18, 166, 230, 171, 255, 218, 219, 209, 187, 204, 64, 99, 68, 98, 119, 170, 197, 55, 212, 200, 142, 185, 142, 40, 136, 83, 0, 26, 176, 29, 71, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}