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: be9ca0b74e56ec0d1177d7db7eda931ae452b39062c8463fc4850a1a0eeb7a8d
Tx prefix hash: 7d06f59ffbec439d9cb8bedafbd75039f6723428610a207cb0c06998457c85ce
Tx public key: 8be81335494ff7d59a784228d065b7adec703d3d26677dc9cedb996878a2ec05
| Timestamp: 1779513337 | Timestamp [UTC]: 2026-05-23 05:15:37 | Age [y:d:h:m:s]: 00:025:03:06:42 |
| Block: 674 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 8071 | RingCT/type: yes/0 |
| Extra: 018be81335494ff7d59a784228d065b7adec703d3d26677dc9cedb996878a2ec050208ff27a2c7f2701438 | ||
1 output(s) for total of 35.144442355513 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8a7d2450b1c47e079ec06612fbc78a5830d7fa5ccaccedcb67dd17119eb3e75b | 35.144442355513 | 739 of 0 | <80> |
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": 734,
"vin": [ {
"gen": {
"height": 674
}
}
],
"vout": [ {
"amount": 35144442355513,
"target": {
"tagged_key": {
"key": "8a7d2450b1c47e079ec06612fbc78a5830d7fa5ccaccedcb67dd17119eb3e75b",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 139, 232, 19, 53, 73, 79, 247, 213, 154, 120, 66, 40, 208, 101, 183, 173, 236, 112, 61, 61, 38, 103, 125, 201, 206, 219, 153, 104, 120, 162, 236, 5, 2, 8, 255, 39, 162, 199, 242, 112, 20, 56
],
"rct_signatures": {
"type": 0
}
}