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: f69b7a69ed1389f209dc9ef5dbcd8fc9c32bc48b043f2f415704326d3b69e465
Tx prefix hash: cafc111db98d73a1645c9156f89681278c3d0864adb75d211f3c6ea47f57c57e
Tx public key: 3a789e79388dd2beadf1fb4a5bd2210623ee8d8dc73bfd2ffcf59271bc683b13
| Timestamp: 1779883327 | Timestamp [UTC]: 2026-05-27 12:02:07 | Age [y:d:h:m:s]: 00:012:12:44:40 |
| Block: 2975 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4911 | RingCT/type: yes/0 |
| Extra: 013a789e79388dd2beadf1fb4a5bd2210623ee8d8dc73bfd2ffcf59271bc683b1302090000000126697be300 | ||
1 output(s) for total of 34.985355128614 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9667611468772b9eabda7073755142825e89f04649aecbac6f6c00bbf2753ae2 | 34.985355128614 | 3531 of 0 | <d1> |
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": 3035,
"vin": [ {
"gen": {
"height": 2975
}
}
],
"vout": [ {
"amount": 34985355128614,
"target": {
"tagged_key": {
"key": "9667611468772b9eabda7073755142825e89f04649aecbac6f6c00bbf2753ae2",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 58, 120, 158, 121, 56, 141, 210, 190, 173, 241, 251, 74, 91, 210, 33, 6, 35, 238, 141, 141, 199, 59, 253, 47, 252, 245, 146, 113, 188, 104, 59, 19, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}