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: d5b2905c7749a68c1eda3c59de440953b05c08fab0de22fe065f7bcb05c52220
Tx prefix hash: 3abafc6d82bde3ada0c22da4c5613f2c5945976149ea308254da44996aa3909f
Tx public key: 8e0d9af9e16fe6ea175bc7ed90bfb8bbfa8163f9aa54387a9033cf89a0b303d0
| Timestamp: 1780806344 | Timestamp [UTC]: 2026-06-07 04:25:44 | Age [y:d:h:m:s]: 00:001:20:21:03 |
| Block: 6955 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 931 | RingCT/type: yes/0 |
| Extra: 018e0d9af9e16fe6ea175bc7ed90bfb8bbfa8163f9aa54387a9033cf89a0b303d0020900000003e49593ff00 | ||
1 output(s) for total of 34.720777890809 HMNY
| stealth address | amount | amount idx | tag |
| 00: dd960fc8092b6f5b2b7a0b6c051393c80c8db62f0c2c32a1846c4be7e1d512a0 | 34.720777890809 | 8577 of 0 | <87> |
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": 7015,
"vin": [ {
"gen": {
"height": 6955
}
}
],
"vout": [ {
"amount": 34720777890809,
"target": {
"tagged_key": {
"key": "dd960fc8092b6f5b2b7a0b6c051393c80c8db62f0c2c32a1846c4be7e1d512a0",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 142, 13, 154, 249, 225, 111, 230, 234, 23, 91, 199, 237, 144, 191, 184, 187, 250, 129, 99, 249, 170, 84, 56, 122, 144, 51, 207, 137, 160, 179, 3, 208, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}