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: c6839a833df3fca7d25cc72641823f4bd977f2d673eb1636f4c057b6361906eb
Tx prefix hash: 81d4b946421d7401a2300231312e9129a251ae794be88e04682e3e3133199eeb
Tx public key: 731c9c6503c6baf3213aacf3aeaf831ab3ab6583296cca86eccdab55c09fefe7
| Timestamp: 1780986364 | Timestamp [UTC]: 2026-06-09 06:26:04 | Age [y:d:h:m:s]: 00:000:05:00:44 |
| Block: 8149 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 366 | RingCT/type: yes/0 |
| Extra: 01731c9c6503c6baf3213aacf3aeaf831ab3ab6583296cca86eccdab55c09fefe7020900000001e49593ff00 | ||
1 output(s) for total of 34.641795579645 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7331b275f2dd97417d33b56fb1e0cccc4eabde95df4a9c8a73ab4bfea7de8e4b | 34.641795579645 | 10091 of 0 | <4c> |
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": 8209,
"vin": [ {
"gen": {
"height": 8149
}
}
],
"vout": [ {
"amount": 34641795579645,
"target": {
"tagged_key": {
"key": "7331b275f2dd97417d33b56fb1e0cccc4eabde95df4a9c8a73ab4bfea7de8e4b",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 115, 28, 156, 101, 3, 198, 186, 243, 33, 58, 172, 243, 174, 175, 131, 26, 179, 171, 101, 131, 41, 108, 202, 134, 236, 205, 171, 85, 192, 159, 239, 231, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}