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: dafad05ac3ba4389713183711a416459febaf7f54a36d42cbcde15032e2b90db
Tx prefix hash: bd47a9329672d4fa2d6af8e7f1b5162617a55c25edd050ac3c8320ee3e5d073b
Tx public key: bb0eda018684b87f166c94d1fc9a69c12cbafa943fbc9456d1ae71c05f13e7da
| Timestamp: 1779443641 | Timestamp [UTC]: 2026-05-22 09:54:01 | Age [y:d:h:m:s]: 00:017:15:41:56 |
| Block: 240 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7646 | RingCT/type: yes/0 |
| Extra: 01bb0eda018684b87f166c94d1fc9a69c12cbafa943fbc9456d1ae71c05f13e7da0209000000014438f87f00 | ||
1 output(s) for total of 35.168336710349 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8cb368e92807b666553d8613792649b19aba00357dd657c170f0d129398a2cd5 | 35.168336710349 | 236 of 0 | <5c> |
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": 300,
"vin": [ {
"gen": {
"height": 240
}
}
],
"vout": [ {
"amount": 35168336710349,
"target": {
"tagged_key": {
"key": "8cb368e92807b666553d8613792649b19aba00357dd657c170f0d129398a2cd5",
"view_tag": "5c"
}
}
}
],
"extra": [ 1, 187, 14, 218, 1, 134, 132, 184, 127, 22, 108, 148, 209, 252, 154, 105, 193, 44, 186, 250, 148, 63, 188, 148, 86, 209, 174, 113, 192, 95, 19, 231, 218, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}