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: dfaa145d1b9cafa27c3d720f58fa7d8f16ae3b094688718ab426af7fd3fbe83f
Tx prefix hash: fd4a763be227aa86ac2a62f4f86e819a95897e8554bb9d3c7b82d2d0a9c4b888
Tx public key: f44d0cb139c9f0f9d8345c39c2b19ec95547b348710b9d1b040548ef890decb1
| Timestamp: 1779736530 | Timestamp [UTC]: 2026-05-25 19:15:30 | Age [y:d:h:m:s]: 00:022:13:20:44 |
| Block: 1919 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6826 | RingCT/type: yes/0 |
| Extra: 01f44d0cb139c9f0f9d8345c39c2b19ec95547b348710b9d1b040548ef890decb102090000000326697be300 | ||
1 output(s) for total of 35.055892316986 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0935457d510838d3be4cb85458093775250d63b718ff3da1db1e01ab6c8ea981 | 35.055892316986 | 2155 of 0 | <fe> |
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": 1979,
"vin": [ {
"gen": {
"height": 1919
}
}
],
"vout": [ {
"amount": 35055892316986,
"target": {
"tagged_key": {
"key": "0935457d510838d3be4cb85458093775250d63b718ff3da1db1e01ab6c8ea981",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 244, 77, 12, 177, 57, 201, 240, 249, 216, 52, 92, 57, 194, 177, 158, 201, 85, 71, 179, 72, 113, 11, 157, 27, 4, 5, 72, 239, 137, 13, 236, 177, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}