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: b5ab61ac02c983c9ba376b9a0443eaa2b3b93ac3a00c116c6aa040a837531a16
Tx prefix hash: dc772510bc88400f0afd029f5ac2ae9f0beef8a123979c44a260a80613afdc7d
Tx public key: de9e327be507c91fead7b7fec5d55bc8dd2929eda0fd8d4515a3cbf1f597147f
| Timestamp: 1779436415 | Timestamp [UTC]: 2026-05-22 07:53:35 | Age [y:d:h:m:s]: 00:017:17:42:22 |
| Block: 139 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7747 | RingCT/type: yes/0 |
| Extra: 01de9e327be507c91fead7b7fec5d55bc8dd2929eda0fd8d4515a3cbf1f597147f020900000001a662ed0300 | ||
1 output(s) for total of 35.175112275593 HMNY
| stealth address | amount | amount idx | tag |
| 00: c051ef6bb8727cda8b567f0e1ba3144ab1a20e0ff1d41ff0c8bc7974a80a29d3 | 35.175112275593 | 135 of 0 | <0b> |
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": 199,
"vin": [ {
"gen": {
"height": 139
}
}
],
"vout": [ {
"amount": 35175112275593,
"target": {
"tagged_key": {
"key": "c051ef6bb8727cda8b567f0e1ba3144ab1a20e0ff1d41ff0c8bc7974a80a29d3",
"view_tag": "0b"
}
}
}
],
"extra": [ 1, 222, 158, 50, 123, 229, 7, 201, 31, 234, 215, 183, 254, 197, 213, 91, 200, 221, 41, 41, 237, 160, 253, 141, 69, 21, 163, 203, 241, 245, 151, 20, 127, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}