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: 0fd87a6e1b879ace5392d52f9d44cf459ed721ada9518d6c7861a85e559181b0
Tx prefix hash: 9300d36308c6435236e7a8c46553acdee54d4a16bc6b18b8a9b993bd47af82d9
Tx public key: d2611499fbb586810c89c7c913d02158e3406c436728540c4cfbb8e8d5e21236
| Timestamp: 1780026833 | Timestamp [UTC]: 2026-05-29 03:53:53 | Age [y:d:h:m:s]: 00:011:00:39:09 |
| Block: 4175 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3857 | RingCT/type: yes/0 |
| Extra: 01d2611499fbb586810c89c7c913d02158e3406c436728540c4cfbb8e8d5e2123602090000000526697be300 | ||
1 output(s) for total of 34.905371498126 HMNY
| stealth address | amount | amount idx | tag |
| 00: 811cedb55c0778c74f38018c649b690e60aa3be91dbf3686718a73c0aaad1f09 | 34.905371498126 | 5208 of 0 | <4b> |
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": 4235,
"vin": [ {
"gen": {
"height": 4175
}
}
],
"vout": [ {
"amount": 34905371498126,
"target": {
"tagged_key": {
"key": "811cedb55c0778c74f38018c649b690e60aa3be91dbf3686718a73c0aaad1f09",
"view_tag": "4b"
}
}
}
],
"extra": [ 1, 210, 97, 20, 153, 251, 181, 134, 129, 12, 137, 199, 201, 19, 208, 33, 88, 227, 64, 108, 67, 103, 40, 84, 12, 76, 251, 184, 232, 213, 226, 18, 54, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}