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: 2947d7bd3858703974c2010a9e3880bd2954370ba301a6160218739c6a15343c
Tx prefix hash: cb1420310e2d082d2b68327687376fd07af45bcee6c12f9972b39068cc827ec3
Tx public key: eaf6fdc4708ff5070e7ad55025972bfdb68dcf6e0e4e7c2f52db937a7efd9d4f
| Timestamp: 1779473041 | Timestamp [UTC]: 2026-05-22 18:04:01 | Age [y:d:h:m:s]: 00:017:08:08:01 |
| Block: 586 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7300 | RingCT/type: yes/0 |
| Extra: 01eaf6fdc4708ff5070e7ad55025972bfdb68dcf6e0e4e7c2f52db937a7efd9d4f02090000000593369e7d00 | ||
1 output(s) for total of 35.145135260363 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7c1996dc24fa6d0355812dc7c14c03d20b22a259894c40adcb38a7c1f2d9b522 | 35.145135260363 | 598 of 0 | <ea> |
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": 646,
"vin": [ {
"gen": {
"height": 586
}
}
],
"vout": [ {
"amount": 35145135260363,
"target": {
"tagged_key": {
"key": "7c1996dc24fa6d0355812dc7c14c03d20b22a259894c40adcb38a7c1f2d9b522",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 234, 246, 253, 196, 112, 143, 245, 7, 14, 122, 213, 80, 37, 151, 43, 253, 182, 141, 207, 110, 14, 78, 124, 47, 82, 219, 147, 122, 126, 253, 157, 79, 2, 9, 0, 0, 0, 5, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}