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: e772433dadc0d54f9290d5e83297229e98aa1914fbce4d4547039ab6db781b87
Tx prefix hash: 61ce41cf724dcfc1fbb3b1dd8c7f39cfe3371cfbf35e85720aa2f0b59759da8f
Tx public key: 36d0e1f3d90dca6643b1f505c8090116cebc0fe24bed200a2d9db832841511e1
| Timestamp: 1780068663 | Timestamp [UTC]: 2026-05-29 15:31:03 | Age [y:d:h:m:s]: 00:010:06:53:46 |
| Block: 4621 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3265 | RingCT/type: yes/0 |
| Extra: 0136d0e1f3d90dca6643b1f505c8090116cebc0fe24bed200a2d9db832841511e102090000000126697be300 | ||
1 output(s) for total of 34.875690882105 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8714dafce11fa0f4c612b9c3a68449d0c17ea613d116c6478a08cc008ca920af | 34.875690882105 | 5802 of 0 | <fe> |
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": 4681,
"vin": [ {
"gen": {
"height": 4621
}
}
],
"vout": [ {
"amount": 34875690882105,
"target": {
"tagged_key": {
"key": "8714dafce11fa0f4c612b9c3a68449d0c17ea613d116c6478a08cc008ca920af",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 54, 208, 225, 243, 217, 13, 202, 102, 67, 177, 245, 5, 200, 9, 1, 22, 206, 188, 15, 226, 75, 237, 32, 10, 45, 157, 184, 50, 132, 21, 17, 225, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}