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: 48eaeed4c367fc1f91f0f71778f87ade210ee446fbac46763d305367b236db0f
Tx prefix hash: c221662a4f28c74e0c480d187b8f142b4769d5b188274805c1b822fe68dc2d0e
Tx public key: 1b2cb4a38fab9874fad41215216260309f632d17ae92303e25336d33b3fa16fa
| Timestamp: 1779742118 | Timestamp [UTC]: 2026-05-25 20:48:38 | Age [y:d:h:m:s]: 00:014:05:51:58 |
| Block: 1941 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5955 | RingCT/type: yes/0 |
| Extra: 011b2cb4a38fab9874fad41215216260309f632d17ae92303e25336d33b3fa16fa02090000000326697be300 | ||
1 output(s) for total of 35.057033742664 HMNY
| stealth address | amount | amount idx | tag |
| 00: 16825e373ed7ab4732f3f9621a57751694d9be79a4b199d914459b15a26b84e0 | 35.057033742664 | 2195 of 0 | <6e> |
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": 2001,
"vin": [ {
"gen": {
"height": 1941
}
}
],
"vout": [ {
"amount": 35057033742664,
"target": {
"tagged_key": {
"key": "16825e373ed7ab4732f3f9621a57751694d9be79a4b199d914459b15a26b84e0",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 27, 44, 180, 163, 143, 171, 152, 116, 250, 212, 18, 21, 33, 98, 96, 48, 159, 99, 45, 23, 174, 146, 48, 62, 37, 51, 109, 51, 179, 250, 22, 250, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}