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: b9b38c7a8eb764078c34c77acdede4503aef6529180a6b7dcc3708b2e33bd500
Tx prefix hash: 13094ebdb9427d64f978dcdddc59e543c8c49429b614e4d1f11d4baf0bf8d829
Tx public key: d8b6f5c145ebb1ce95a961f83cd9821114b25bf539e44ba9bcbe940a1cc968ba
| Timestamp: 1781003712 | Timestamp [UTC]: 2026-06-09 11:15:12 | Age [y:d:h:m:s]: 00:006:06:01:13 |
| Block: 8494 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 251 | RingCT/type: yes/0 |
| Extra: 01d8b6f5c145ebb1ce95a961f83cd9821114b25bf539e44ba9bcbe940a1cc968ba020900000001e49593ff00 | ||
1 output(s) for total of 34.619007532808 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2644daa7f44dd1753c1b803c0c60b1ed73ffc90ebf60ecdd562ee9bc0039f3e0 | 34.619007532808 | 10494 of 0 | <0e> |
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": 8554,
"vin": [ {
"gen": {
"height": 8494
}
}
],
"vout": [ {
"amount": 34619007532808,
"target": {
"tagged_key": {
"key": "2644daa7f44dd1753c1b803c0c60b1ed73ffc90ebf60ecdd562ee9bc0039f3e0",
"view_tag": "0e"
}
}
}
],
"extra": [ 1, 216, 182, 245, 193, 69, 235, 177, 206, 149, 169, 97, 248, 60, 217, 130, 17, 20, 178, 91, 245, 57, 228, 75, 169, 188, 190, 148, 10, 28, 201, 104, 186, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}