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: c41548be127a6bf7e352262dd590084f6214f05bce67fcbbfa1e325a08912d7f
Tx prefix hash: 355a159b67b5f52f110e42b5f03f211dc5a5b3a966a48697bb6492284c8422c7
Tx public key: e639dc137d560e18eef92acd800895a96850cfdcc589b0e176ab8ca47af0c1ed
| Timestamp: 1780994733 | Timestamp [UTC]: 2026-06-09 08:45:33 | Age [y:d:h:m:s]: 00:000:08:23:30 |
| Block: 8309 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 426 | RingCT/type: yes/0 |
| Extra: 01e639dc137d560e18eef92acd800895a96850cfdcc589b0e176ab8ca47af0c1ed020900000001e49593ff00 | ||
1 output(s) for total of 34.631225345506 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3d265e13705a7711d54b17e253660ac26aa07bded9bf0f2cb7155841b24b7e9c | 34.631225345506 | 10279 of 0 | <7f> |
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": 8369,
"vin": [ {
"gen": {
"height": 8309
}
}
],
"vout": [ {
"amount": 34631225345506,
"target": {
"tagged_key": {
"key": "3d265e13705a7711d54b17e253660ac26aa07bded9bf0f2cb7155841b24b7e9c",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 230, 57, 220, 19, 125, 86, 14, 24, 238, 249, 42, 205, 128, 8, 149, 169, 104, 80, 207, 220, 197, 137, 176, 225, 118, 171, 140, 164, 122, 240, 193, 237, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}