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: 17be633c1fd7b2afd9c1ff56149eeb9526ea803a46ef0124cee0b6ed2cb0be48
Tx prefix hash: df616ec8a28f133a6ce2dde1cbe930358eaf0148e2068bb6c8b23485387b2fd3
Tx public key: 59eb2c3983d64e1abeba711c62cbb3846c2c2e1c51a277f5a0f616979d4ce351
| Timestamp: 1780851342 | Timestamp [UTC]: 2026-06-07 16:55:42 | Age [y:d:h:m:s]: 00:005:18:06:34 |
| Block: 7543 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1202 | RingCT/type: yes/0 |
| Extra: 0159eb2c3983d64e1abeba711c62cbb3846c2c2e1c51a277f5a0f616979d4ce351020900000001e49593ff00 | ||
1 output(s) for total of 34.681859600208 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6192d135d1f03448e027d32325cd9738dc3a1c1cdf344b1f067082eeb1bedf3c | 34.681859600208 | 9307 of 0 | <34> |
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": 7603,
"vin": [ {
"gen": {
"height": 7543
}
}
],
"vout": [ {
"amount": 34681859600208,
"target": {
"tagged_key": {
"key": "6192d135d1f03448e027d32325cd9738dc3a1c1cdf344b1f067082eeb1bedf3c",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 89, 235, 44, 57, 131, 214, 78, 26, 190, 186, 113, 28, 98, 203, 179, 132, 108, 44, 46, 28, 81, 162, 119, 245, 160, 246, 22, 151, 157, 76, 227, 81, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}