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: d36515c105b136ddb64be85a9a7a962835ad6cfda7d2bd9f585d4b5e9ddd766c
Tx prefix hash: dc0ab6b84c9c08bc173a413c483e4cc8793e43829fc352a5c777cbc8c17b7147
Tx public key: 0ee95ad62a29125b0111da850bc4ea9cc1d0dea4af3c7e8c338a0d7d44f44a76
| Timestamp: 1780069885 | Timestamp [UTC]: 2026-05-29 15:51:25 | Age [y:d:h:m:s]: 00:018:16:37:47 |
| Block: 4631 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4114 | RingCT/type: yes/0 |
| Extra: 010ee95ad62a29125b0111da850bc4ea9cc1d0dea4af3c7e8c338a0d7d44f44a7602090000000426697be300 | ||
1 output(s) for total of 34.875025686801 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84fab9b4eb6423759000dbdcf90c8d5397f2d856fdd140a1c68f9a7b9ceaef2c | 34.875025686801 | 5816 of 0 | <07> |
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": 4691,
"vin": [ {
"gen": {
"height": 4631
}
}
],
"vout": [ {
"amount": 34875025686801,
"target": {
"tagged_key": {
"key": "84fab9b4eb6423759000dbdcf90c8d5397f2d856fdd140a1c68f9a7b9ceaef2c",
"view_tag": "07"
}
}
}
],
"extra": [ 1, 14, 233, 90, 214, 42, 41, 18, 91, 1, 17, 218, 133, 11, 196, 234, 156, 193, 208, 222, 164, 175, 60, 126, 140, 51, 138, 13, 125, 68, 244, 74, 118, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}