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: 1a88f2cd5aaa1f9f9532c75868941be657295d7e1c502647e0c7a02b824a6a33
Tx prefix hash: cbf18b6bac1b2a4ff68c7846bfb056ef67852ae704ca6ff7f3a32a0ec439b998
Tx public key: 2cb0b4f5f0f940bcc610a523add4623e3dafcd60e0367d64781613aa47e62d6a
| Timestamp: 1779724288 | Timestamp [UTC]: 2026-05-25 15:51:28 | Age [y:d:h:m:s]: 00:014:09:44:29 |
| Block: 1820 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6066 | RingCT/type: yes/0 |
| Extra: 012cb0b4f5f0f940bcc610a523add4623e3dafcd60e0367d64781613aa47e62d6a020900000001ba6d17be00 | ||
1 output(s) for total of 35.062512465333 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2be2e1f5534da48e51ae6f059b0768c6b1a1aba806b4926a34cf762bd8fe52bd | 35.062512465333 | 2014 of 0 | <ed> |
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": 1880,
"vin": [ {
"gen": {
"height": 1820
}
}
],
"vout": [ {
"amount": 35062512465333,
"target": {
"tagged_key": {
"key": "2be2e1f5534da48e51ae6f059b0768c6b1a1aba806b4926a34cf762bd8fe52bd",
"view_tag": "ed"
}
}
}
],
"extra": [ 1, 44, 176, 180, 245, 240, 249, 64, 188, 198, 16, 165, 35, 173, 212, 98, 62, 61, 175, 205, 96, 224, 54, 125, 100, 120, 22, 19, 170, 71, 230, 45, 106, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}