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: 1c94f5cc22f21818a9fe6d73295cf579e983517df35e556e2ee68ec23b174c88
Tx prefix hash: 8131ba5c65b5771c9283088b4f762640dd7a0729a853c57c0b860762d4270214
Tx public key: d40af13c3d7646763ab3ca8bf809f2b398be44ce1785ec00f02d2d046307c1b0
| Timestamp: 1780848177 | Timestamp [UTC]: 2026-06-07 16:02:57 | Age [y:d:h:m:s]: 00:001:09:33:00 |
| Block: 7524 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 362 | RingCT/type: yes/0 |
| Extra: 01d40af13c3d7646763ab3ca8bf809f2b398be44ce1785ec00f02d2d046307c1b0020900000002e49593ff00 | ||
1 output(s) for total of 34.689739281733 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5030e41b1631a5f9e6ecf4b84c49c20ea93309ff02444015fd9871203c60903b | 34.689739281733 | 9276 of 0 | <2a> |
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": 7584,
"vin": [ {
"gen": {
"height": 7524
}
}
],
"vout": [ {
"amount": 34689739281733,
"target": {
"tagged_key": {
"key": "5030e41b1631a5f9e6ecf4b84c49c20ea93309ff02444015fd9871203c60903b",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 212, 10, 241, 60, 61, 118, 70, 118, 58, 179, 202, 139, 248, 9, 242, 179, 152, 190, 68, 206, 23, 133, 236, 0, 240, 45, 45, 4, 99, 7, 193, 176, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}