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: 44709d28ad676eb80db5ba56675f7b55031170c0d01fab909b4dddcaae0eb1e8
Tx prefix hash: fadaa7c103a0ec74c35e971834a72d4ebf139e7d0f9d135d1718622f2077eac0
Tx public key: 0f36743537f110bd25e3f6b99cac1ec0d510fb3dc87c9b88b8047c0815bf6488
| Timestamp: 1780739044 | Timestamp [UTC]: 2026-06-06 09:44:04 | Age [y:d:h:m:s]: 00:002:15:51:53 |
| Block: 6396 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1490 | RingCT/type: yes/0 |
| Extra: 010f36743537f110bd25e3f6b99cac1ec0d510fb3dc87c9b88b8047c0815bf6488020900000006e49593ff00 | ||
1 output(s) for total of 34.757817235630 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9991c5a74d349336f2bb7af33268a8c72f83277d9bff3c947a4c57376ea5f8c4 | 34.757817235630 | 7887 of 0 | <5d> |
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": 6456,
"vin": [ {
"gen": {
"height": 6396
}
}
],
"vout": [ {
"amount": 34757817235630,
"target": {
"tagged_key": {
"key": "9991c5a74d349336f2bb7af33268a8c72f83277d9bff3c947a4c57376ea5f8c4",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 15, 54, 116, 53, 55, 241, 16, 189, 37, 227, 246, 185, 156, 172, 30, 192, 213, 16, 251, 61, 200, 124, 155, 136, 184, 4, 124, 8, 21, 191, 100, 136, 2, 9, 0, 0, 0, 6, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}