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: 33e6bfaa83eec7c4798a6ced69d6235c0ace59d90cea54067ec862be45feb9db
Tx prefix hash: 3b04df3f5a32314007a4ac8c1d673d7218367641deb73ac6440479a1c75fa718
Tx public key: cf67e63f7862f0d5e9f4b22b56c959e890efbe276954897e9980ba98db3d8c0a
| Timestamp: 1780996525 | Timestamp [UTC]: 2026-06-09 09:15:25 | Age [y:d:h:m:s]: 00:007:23:20:49 |
| Block: 8351 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 394 | RingCT/type: yes/0 |
| Extra: 01cf67e63f7862f0d5e9f4b22b56c959e890efbe276954897e9980ba98db3d8c0a020900000001e49593ff00 | ||
1 output(s) for total of 34.628451193525 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb14d1546be670e9a3b876d5568553a6c5cb4c06cad2cc1f662b4bda865c5d3b | 34.628451193525 | 10327 of 0 | <b0> |
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": 8411,
"vin": [ {
"gen": {
"height": 8351
}
}
],
"vout": [ {
"amount": 34628451193525,
"target": {
"tagged_key": {
"key": "eb14d1546be670e9a3b876d5568553a6c5cb4c06cad2cc1f662b4bda865c5d3b",
"view_tag": "b0"
}
}
}
],
"extra": [ 1, 207, 103, 230, 63, 120, 98, 240, 213, 233, 244, 178, 43, 86, 201, 89, 232, 144, 239, 190, 39, 105, 84, 137, 126, 153, 128, 186, 152, 219, 61, 140, 10, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}