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: 7d0f52247d401d75177113bf793a582cedd08220db1a350a468ffd78d9c7e748
Tx prefix hash: 6348c9f12dd49b5c222e97c2a6a32d4d9d6189fd5ea6bf5da88f6c46fb64502c
Tx public key: 16c38c27e3f4f8edd076381e1f4d8aedc3450419e6f2d86ab51ef69c4c4a9fb0
| Timestamp: 1780818633 | Timestamp [UTC]: 2026-06-07 07:50:33 | Age [y:d:h:m:s]: 00:001:17:45:24 |
| Block: 7118 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 768 | RingCT/type: yes/0 |
| Extra: 0116c38c27e3f4f8edd076381e1f4d8aedc3450419e6f2d86ab51ef69c4c4a9fb0020900000001e49593ff00 | ||
1 output(s) for total of 34.709984943952 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7b6414313fe921981688c4c29b08be3ecb104e95a670df6fcc9b660474220130 | 34.709984943952 | 8774 of 0 | <d7> |
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": 7178,
"vin": [ {
"gen": {
"height": 7118
}
}
],
"vout": [ {
"amount": 34709984943952,
"target": {
"tagged_key": {
"key": "7b6414313fe921981688c4c29b08be3ecb104e95a670df6fcc9b660474220130",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 22, 195, 140, 39, 227, 244, 248, 237, 208, 118, 56, 30, 31, 77, 138, 237, 195, 69, 4, 25, 230, 242, 216, 106, 181, 30, 246, 156, 76, 74, 159, 176, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}