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: 32eef4963f177323f53fe14615fd3967bfb67d497fe81a7d79b24b9d914c3e27
Tx prefix hash: 3107b949173baa934a1fa2c99acc99cc9dc3920e36d1812c6aaa9e751242231e
Tx public key: f69925365867378ca6bf9a4789c9b4b61a786bd4371c95f2ddb0bf36b792fb49
| Timestamp: 1780718488 | Timestamp [UTC]: 2026-06-06 04:01:28 | Age [y:d:h:m:s]: 00:002:22:48:20 |
| Block: 6216 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1703 | RingCT/type: yes/0 |
| Extra: 01f69925365867378ca6bf9a4789c9b4b61a786bd4371c95f2ddb0bf36b792fb49020900000002e49593ff00 | ||
1 output(s) for total of 34.769752445243 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6cc1a293762dd665a1be1777e4fdf01c1fec6d8450319e856c56a80509e3111a | 34.769752445243 | 7695 of 0 | <6e> |
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": 6276,
"vin": [ {
"gen": {
"height": 6216
}
}
],
"vout": [ {
"amount": 34769752445243,
"target": {
"tagged_key": {
"key": "6cc1a293762dd665a1be1777e4fdf01c1fec6d8450319e856c56a80509e3111a",
"view_tag": "6e"
}
}
}
],
"extra": [ 1, 246, 153, 37, 54, 88, 103, 55, 140, 166, 191, 154, 71, 137, 201, 180, 182, 26, 120, 107, 212, 55, 28, 149, 242, 221, 176, 191, 54, 183, 146, 251, 73, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}