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: 371b8c14f0a03743da8e947f9307c31ac9186b52078a47db94cef0ccf42f0ac9
Tx prefix hash: 0e8b31cc11936a4ae1c6c46f30312197e98a8bed534d7b75656b290aeb4475f4
Tx public key: eb760745aaabe2ed096b8379113cebe86002991bbd955bbb34dd1e9b6f6629aa
| Timestamp: 1780322713 | Timestamp [UTC]: 2026-06-01 14:05:13 | Age [y:d:h:m:s]: 00:007:09:13:40 |
| Block: 5011 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2875 | RingCT/type: yes/0 |
| Extra: 01eb760745aaabe2ed096b8379113cebe86002991bbd955bbb34dd1e9b6f6629aa02090000003726697be300 | ||
1 output(s) for total of 34.849757664472 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2e08f9e3522ecfd6d3e86629e7be3a9e57d6217acb02d8e902054fa60cb80c4e | 34.849757664472 | 6384 of 0 | <90> |
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": 5071,
"vin": [ {
"gen": {
"height": 5011
}
}
],
"vout": [ {
"amount": 34849757664472,
"target": {
"tagged_key": {
"key": "2e08f9e3522ecfd6d3e86629e7be3a9e57d6217acb02d8e902054fa60cb80c4e",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 235, 118, 7, 69, 170, 171, 226, 237, 9, 107, 131, 121, 17, 60, 235, 232, 96, 2, 153, 27, 189, 149, 91, 187, 52, 221, 30, 155, 111, 102, 41, 170, 2, 9, 0, 0, 0, 55, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}