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: 843be728ea7ed12a1864dd8f1de82c6210efc36c01b07ba6cae1d345c5655428
Tx prefix hash: e4fbefa2f196faaa68c2b66f7bfb95e3f97813659304e762b45be4d0e5c28210
Tx public key: 0c9f8002be10d3a2167b43e9db3c1cc3baf21feb293239e201680f4dc50b4251
| Timestamp: 1779875229 | Timestamp [UTC]: 2026-05-27 09:47:09 | Age [y:d:h:m:s]: 00:012:15:48:48 |
| Block: 2878 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5008 | RingCT/type: yes/0 |
| Extra: 010c9f8002be10d3a2167b43e9db3c1cc3baf21feb293239e201680f4dc50b425102090000000126697be300 | ||
1 output(s) for total of 34.991828472714 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7bf6509c6649507bd22cf08a3c4feb5b1cb219057ef9e457cb63c51c6fdcb9f6 | 34.991828472714 | 3406 of 0 | <86> |
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": 2938,
"vin": [ {
"gen": {
"height": 2878
}
}
],
"vout": [ {
"amount": 34991828472714,
"target": {
"tagged_key": {
"key": "7bf6509c6649507bd22cf08a3c4feb5b1cb219057ef9e457cb63c51c6fdcb9f6",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 12, 159, 128, 2, 190, 16, 211, 162, 22, 123, 67, 233, 219, 60, 28, 195, 186, 242, 31, 235, 41, 50, 57, 226, 1, 104, 15, 77, 197, 11, 66, 81, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}