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: 1254441937c6f8f06d8bfa1cac770f09425e396696c8d14bb7a6e7aa49225c64
Tx prefix hash: 6115f42a100eeec59a3bf3068858d2090780ee32b00fedddd1767660f8eca443
Tx public key: bce035073e819e2833aaae22327bda100052487e7498e96f80dce7057198f0ba
| Timestamp: 1780900285 | Timestamp [UTC]: 2026-06-08 06:31:25 | Age [y:d:h:m:s]: 00:000:14:40:42 |
| Block: 7806 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 80 | RingCT/type: yes/0 |
| Extra: 01bce035073e819e2833aaae22327bda100052487e7498e96f80dce7057198f0ba0209000000024a728a4c00 | ||
1 output(s) for total of 34.668690391945 HMNY
| stealth address | amount | amount idx | tag |
| 00: 50c8b3b9632bf130a0ebc0edcbd02654e3b12d0feaa41934f70b75d1fc9ac445 | 34.668690391945 | 9674 of 0 | <f9> |
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": 7866,
"vin": [ {
"gen": {
"height": 7806
}
}
],
"vout": [ {
"amount": 34668690391945,
"target": {
"tagged_key": {
"key": "50c8b3b9632bf130a0ebc0edcbd02654e3b12d0feaa41934f70b75d1fc9ac445",
"view_tag": "f9"
}
}
}
],
"extra": [ 1, 188, 224, 53, 7, 62, 129, 158, 40, 51, 170, 174, 34, 50, 123, 218, 16, 0, 82, 72, 126, 116, 152, 233, 111, 128, 220, 231, 5, 113, 152, 240, 186, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}