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: f41b1bc64dd75258ab519da040b4cd83eea6f597d0956c9b32037ecc534187b3
Tx prefix hash: 07a20baf11954bc39dbac1f172090c3427e49fe91d8dce56943c892a0d9e7274
Tx public key: a64ee11427de335227d5a9f1548885f8c12a4e97ca38227eab3931287ecf8d90
| Timestamp: 1780904473 | Timestamp [UTC]: 2026-06-08 07:41:13 | Age [y:d:h:m:s]: 00:000:14:43:36 |
| Block: 7852 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 34 | RingCT/type: yes/0 |
| Extra: 01a64ee11427de335227d5a9f1548885f8c12a4e97ca38227eab3931287ecf8d900209000000014a728a4c00 | ||
1 output(s) for total of 34.661425130225 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8048a463f3ace7534aa643ec040745154fef451fb0f059314564345cfff92fc | 34.661425130225 | 9736 of 0 | <29> |
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": 7912,
"vin": [ {
"gen": {
"height": 7852
}
}
],
"vout": [ {
"amount": 34661425130225,
"target": {
"tagged_key": {
"key": "d8048a463f3ace7534aa643ec040745154fef451fb0f059314564345cfff92fc",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 166, 78, 225, 20, 39, 222, 51, 82, 39, 213, 169, 241, 84, 136, 133, 248, 193, 42, 78, 151, 202, 56, 34, 126, 171, 57, 49, 40, 126, 207, 141, 144, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}