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: 455e46887325b079273a968f1add8ddbddff849676bb8106a91f739a0d9a0003
Tx prefix hash: 7b8b8ce40095e2a8032ffa995a8d34c987a8760d7e71cebaf7f2d7909152cc1a
Tx public key: 93a4ee7473d0556b9411778fee81024241f6e7c91c38ee5d36276b2c3ae58a5f
| Timestamp: 1780818649 | Timestamp [UTC]: 2026-06-07 07:50:49 | Age [y:d:h:m:s]: 00:001:15:28:04 |
| Block: 7119 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 767 | RingCT/type: yes/0 |
| Extra: 0193a4ee7473d0556b9411778fee81024241f6e7c91c38ee5d36276b2c3ae58a5f020900000001e49593ff00 | ||
1 output(s) for total of 34.709918739909 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70cb6ad1bc4f4be80f80bc2c7267eacb8a85d0cce6e8927a7f349667010dcba4 | 34.709918739909 | 8775 of 0 | <4a> |
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": 7179,
"vin": [ {
"gen": {
"height": 7119
}
}
],
"vout": [ {
"amount": 34709918739909,
"target": {
"tagged_key": {
"key": "70cb6ad1bc4f4be80f80bc2c7267eacb8a85d0cce6e8927a7f349667010dcba4",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 147, 164, 238, 116, 115, 208, 85, 107, 148, 17, 119, 143, 238, 129, 2, 66, 65, 246, 231, 201, 28, 56, 238, 93, 54, 39, 107, 44, 58, 229, 138, 95, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}