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: 8050ab6d0e4997cbc346ea74a1efd3b6aed17c44461f985d8c342288bf07b0bc
Tx prefix hash: 14234b718a5630a47f08aee88e2dd381e55e509fe33af3bf94b567d6b95fd9f9
Tx public key: c0bcb61a536f54ac55d44c02be819f8142045ecfd724b6374291b1e521d5fb8e
| Timestamp: 1780825465 | Timestamp [UTC]: 2026-06-07 09:44:25 | Age [y:d:h:m:s]: 00:010:01:51:40 |
| Block: 7251 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1494 | RingCT/type: yes/0 |
| Extra: 01c0bcb61a536f54ac55d44c02be819f8142045ecfd724b6374291b1e521d5fb8e020900000001e49593ff00 | ||
1 output(s) for total of 34.701180914664 HMNY
| stealth address | amount | amount idx | tag |
| 00: bd1aa83809709b663ee731ffae0868b66d9d302ec04d1bc7e7727c5a8c96298b | 34.701180914664 | 8929 of 0 | <4b> |
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": 7311,
"vin": [ {
"gen": {
"height": 7251
}
}
],
"vout": [ {
"amount": 34701180914664,
"target": {
"tagged_key": {
"key": "bd1aa83809709b663ee731ffae0868b66d9d302ec04d1bc7e7727c5a8c96298b",
"view_tag": "4b"
}
}
}
],
"extra": [ 1, 192, 188, 182, 26, 83, 111, 84, 172, 85, 212, 76, 2, 190, 129, 159, 129, 66, 4, 94, 207, 215, 36, 182, 55, 66, 145, 177, 229, 33, 213, 251, 142, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}