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: f632d5e8913722a0857e0c7f220e7af85aae7feb7290b5383135d53fb4e83851
Tx prefix hash: 403d43a108d23e5423d0f0a591566cb5af95279e67c4cfc120821d26eab5f58c
Tx public key: 2ee2d95560c806dc484bdbcb0ac89457c812399520aee78045dcb0a69a2b66f7
| Timestamp: 1780726805 | Timestamp [UTC]: 2026-06-06 06:20:05 | Age [y:d:h:m:s]: 00:002:20:29:43 |
| Block: 6281 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1639 | RingCT/type: yes/0 |
| Extra: 012ee2d95560c806dc484bdbcb0ac89457c812399520aee78045dcb0a69a2b66f7020900000001e49593ff00 | ||
1 output(s) for total of 34.765442035749 HMNY
| stealth address | amount | amount idx | tag |
| 00: 01a55efed9ddbefceb1766d8e4bcd7243348eb7eda1daac152e618c8598833bf | 34.765442035749 | 7764 of 0 | <38> |
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": 6341,
"vin": [ {
"gen": {
"height": 6281
}
}
],
"vout": [ {
"amount": 34765442035749,
"target": {
"tagged_key": {
"key": "01a55efed9ddbefceb1766d8e4bcd7243348eb7eda1daac152e618c8598833bf",
"view_tag": "38"
}
}
}
],
"extra": [ 1, 46, 226, 217, 85, 96, 200, 6, 220, 72, 75, 219, 203, 10, 200, 148, 87, 200, 18, 57, 149, 32, 174, 231, 128, 69, 220, 176, 166, 154, 43, 102, 247, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}