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: 81917050d76e73cee879027c31120f77db22575e4e654b97184cb3bf4831290f
Tx prefix hash: 11c5c322ce928eb92ab96587c92c2dca7b524e3826ad474814020799b234fe5e
Tx public key: 97c0eecca967e8daede3c84365c3ce5cefe957186bc050ed4d899d718d108d4e
| Timestamp: 1779804990 | Timestamp [UTC]: 2026-05-26 14:16:30 | Age [y:d:h:m:s]: 00:021:17:48:51 |
| Block: 2342 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6403 | RingCT/type: yes/0 |
| Extra: 0197c0eecca967e8daede3c84365c3ce5cefe957186bc050ed4d899d718d108d4e02090000000226697be300 | ||
1 output(s) for total of 35.027620305703 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2be96d0184e7699e51102a74c9dc11808cbd59a2f31f729e2a5c3c6fcb903661 | 35.027620305703 | 2740 of 0 | <b0> |
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": 2402,
"vin": [ {
"gen": {
"height": 2342
}
}
],
"vout": [ {
"amount": 35027620305703,
"target": {
"tagged_key": {
"key": "2be96d0184e7699e51102a74c9dc11808cbd59a2f31f729e2a5c3c6fcb903661",
"view_tag": "b0"
}
}
}
],
"extra": [ 1, 151, 192, 238, 204, 169, 103, 232, 218, 237, 227, 200, 67, 101, 195, 206, 92, 239, 233, 87, 24, 107, 192, 80, 237, 77, 137, 157, 113, 141, 16, 141, 78, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}