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: ce0286c2d119bac1f294202394234775e32c9e5a51ca7af8107e4ae20ea65541
Tx prefix hash: 674eb58f2ec7dcc94c44a7ea60a8fdce2ca76b8773921148c513f1b7c0e153c1
Tx public key: 0f8d1ff52aa730f081e2a9377e83e1f50eb9b0237c235b1f3acc4d3b5e40e161
| Timestamp: 1779731378 | Timestamp [UTC]: 2026-05-25 17:49:38 | Age [y:d:h:m:s]: 00:014:10:43:24 |
| Block: 1888 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6142 | RingCT/type: yes/0 |
| Extra: 010f8d1ff52aa730f081e2a9377e83e1f50eb9b0237c235b1f3acc4d3b5e40e161020900000008ba6d17be00 | ||
1 output(s) for total of 35.060577558301 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8c641d809a3e8418584d14aa71c9e6afe375da6f77b55bd0019c9dd37172795c | 35.060577558301 | 2105 of 0 | <c2> |
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": 1948,
"vin": [ {
"gen": {
"height": 1888
}
}
],
"vout": [ {
"amount": 35060577558301,
"target": {
"tagged_key": {
"key": "8c641d809a3e8418584d14aa71c9e6afe375da6f77b55bd0019c9dd37172795c",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 15, 141, 31, 245, 42, 167, 48, 240, 129, 226, 169, 55, 126, 131, 225, 245, 14, 185, 176, 35, 124, 35, 91, 31, 58, 204, 77, 59, 94, 64, 225, 97, 2, 9, 0, 0, 0, 8, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}