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: 66b7bb0e17de98ffbbe1af817a8a4bf0d6562218f1eba365011711c158a9abe6
Tx prefix hash: f99064574ebdb6d4b38dda14623701a557b532514a3bdadb22db2b0336009484
Tx public key: e93c2b3d91d4c7eb1fc0ff792441550e3e3b893239e13f902ea26e2361f1ae81
| Timestamp: 1780699788 | Timestamp [UTC]: 2026-06-05 22:49:48 | Age [y:d:h:m:s]: 00:003:02:46:09 |
| Block: 6038 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1848 | RingCT/type: yes/0 |
| Extra: 01e93c2b3d91d4c7eb1fc0ff792441550e3e3b893239e13f902ea26e2361f1ae81020900000001e49593ff00 | ||
1 output(s) for total of 34.781559071694 HMNY
| stealth address | amount | amount idx | tag |
| 00: bc32341b1314fee112ee302cd0c3dad43d1b36e800ab719eac7392023c00acf8 | 34.781559071694 | 7507 of 0 | <bf> |
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": 6098,
"vin": [ {
"gen": {
"height": 6038
}
}
],
"vout": [ {
"amount": 34781559071694,
"target": {
"tagged_key": {
"key": "bc32341b1314fee112ee302cd0c3dad43d1b36e800ab719eac7392023c00acf8",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 233, 60, 43, 61, 145, 212, 199, 235, 31, 192, 255, 121, 36, 65, 85, 14, 62, 59, 137, 50, 57, 225, 63, 144, 46, 162, 110, 35, 97, 241, 174, 129, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}