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: d0ee4d1d9ee82d06a15f20a05c36f393f1df554bbc75b23020f2a63af246ff38
Tx prefix hash: 4b415c937ebd4f603417d186412e9a2bf1ed783cea642f97a4664f57164dcb70
Tx public key: 3b1c161f19897314b26082ca56a107b48a8971d28a99d145c6ebb3d420a206c1
| Timestamp: 1780980574 | Timestamp [UTC]: 2026-06-09 04:49:34 | Age [y:d:h:m:s]: 00:000:04:10:25 |
| Block: 8022 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 307 | RingCT/type: yes/0 |
| Extra: 013b1c161f19897314b26082ca56a107b48a8971d28a99d145c6ebb3d420a206c1020900000001e49593ff00 | ||
1 output(s) for total of 34.660812799711 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1b139f611eb5aa20f692c30b7b20825eab097b4c93392ddbdcd2577b9696bcb4 | 34.660812799711 | 9944 of 0 | <d8> |
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": 8082,
"vin": [ {
"gen": {
"height": 8022
}
}
],
"vout": [ {
"amount": 34660812799711,
"target": {
"tagged_key": {
"key": "1b139f611eb5aa20f692c30b7b20825eab097b4c93392ddbdcd2577b9696bcb4",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 59, 28, 22, 31, 25, 137, 115, 20, 178, 96, 130, 202, 86, 161, 7, 180, 138, 137, 113, 210, 138, 153, 209, 69, 198, 235, 179, 212, 32, 162, 6, 193, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}