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: 82c8e0f197b71f6bf56b09d6d3864cef751eb95e56126805e378a67e149341a0
Tx prefix hash: d81a344a66cc884095673acd4398fd724a1a3d4e7060b0cab6cad892b565839a
Tx public key: 2cbf2ddf49d84bd219d1b731ec1e4ee3cfef3361f14ad790a65248fe3cfcaf01
| Timestamp: 1780000543 | Timestamp [UTC]: 2026-05-28 20:35:43 | Age [y:d:h:m:s]: 00:015:14:26:33 |
| Block: 4057 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4688 | RingCT/type: yes/0 |
| Extra: 012cbf2ddf49d84bd219d1b731ec1e4ee3cfef3361f14ad790a65248fe3cfcaf0102090000000426697be300 | ||
1 output(s) for total of 34.913228441843 HMNY
| stealth address | amount | amount idx | tag |
| 00: 20eb25c0642df775c3bd7bc46346c8b6ed91e3c26bea2fa91396c3bb53ec94b0 | 34.913228441843 | 5027 of 0 | <d5> |
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": 4117,
"vin": [ {
"gen": {
"height": 4057
}
}
],
"vout": [ {
"amount": 34913228441843,
"target": {
"tagged_key": {
"key": "20eb25c0642df775c3bd7bc46346c8b6ed91e3c26bea2fa91396c3bb53ec94b0",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 44, 191, 45, 223, 73, 216, 75, 210, 25, 209, 183, 49, 236, 30, 78, 227, 207, 239, 51, 97, 241, 74, 215, 144, 166, 82, 72, 254, 60, 252, 175, 1, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}