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: 487d63e50714089126d9d9e0db971d72944762dd50af0297bf8a417fa6b2305a
Tx prefix hash: 4fe7a98a839bfc93e3821a30c00497fabddfc602c826b813c3b1df147c67d3be
Tx public key: 1843ff742a68e20c5ac1361a6650d7a308b21092dac64d54f09baa251b8d9ee7
| Timestamp: 1779765460 | Timestamp [UTC]: 2026-05-26 03:17:40 | Age [y:d:h:m:s]: 00:013:20:01:13 |
| Block: 1964 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5922 | RingCT/type: yes/0 |
| Extra: 011843ff742a68e20c5ac1361a6650d7a308b21092dac64d54f09baa251b8d9ee702090000000126697be300 | ||
1 output(s) for total of 35.052883571867 HMNY
| stealth address | amount | amount idx | tag |
| 00: 33dde7e85fa700f58c61672443bbedd9565588795f982c84169c40de5a840d41 | 35.052883571867 | 2230 of 0 | <4c> |
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": 2024,
"vin": [ {
"gen": {
"height": 1964
}
}
],
"vout": [ {
"amount": 35052883571867,
"target": {
"tagged_key": {
"key": "33dde7e85fa700f58c61672443bbedd9565588795f982c84169c40de5a840d41",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 24, 67, 255, 116, 42, 104, 226, 12, 90, 193, 54, 26, 102, 80, 215, 163, 8, 178, 16, 146, 218, 198, 77, 84, 240, 155, 170, 37, 27, 141, 158, 231, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}