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: fe6655f45554edbf568e1319ea8c0c7b2370ea7f58c672e8940ed44c7bdc000d
Tx prefix hash: 082099a8fb3bba7a36b5acd9ffe0a80137039a029fe95ae2b26dfb0209ba3bdd
Tx public key: 3673ab47cb45ebe22a15d9cef94c285843e71930036b508bb0296d484b2379a0
| Timestamp: 1780832089 | Timestamp [UTC]: 2026-06-07 11:34:49 | Age [y:d:h:m:s]: 00:001:09:37:18 |
| Block: 7358 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 528 | RingCT/type: yes/0 |
| Extra: 013673ab47cb45ebe22a15d9cef94c285843e71930036b508bb0296d484b2379a0020900000002e49593ff00 | ||
1 output(s) for total of 34.694099594789 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0ed82d4e2cf7d92398043bf32467618318984fb0ed4b8b4d67112cda1a0ef50 | 34.694099594789 | 9058 of 0 | <f9> |
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": 7418,
"vin": [ {
"gen": {
"height": 7358
}
}
],
"vout": [ {
"amount": 34694099594789,
"target": {
"tagged_key": {
"key": "e0ed82d4e2cf7d92398043bf32467618318984fb0ed4b8b4d67112cda1a0ef50",
"view_tag": "f9"
}
}
}
],
"extra": [ 1, 54, 115, 171, 71, 203, 69, 235, 226, 42, 21, 217, 206, 249, 76, 40, 88, 67, 231, 25, 48, 3, 107, 80, 139, 176, 41, 109, 72, 75, 35, 121, 160, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}