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: e5f22955e59eb4f7c0fffc7b01a77f83daa0ed790f0df4d40d41718efee3d3f8
Tx prefix hash: d4d0719b4d9ff356b002eb3e093cb462df278ad22984ccecf38f76d35057b598
Tx public key: 14e888e93f498ad8bf3e571672bbf716d81555ac30c8097d5f718c10e88a56fd
| Timestamp: 1780693646 | Timestamp [UTC]: 2026-06-05 21:07:26 | Age [y:d:h:m:s]: 00:011:10:54:19 |
| Block: 5884 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2861 | RingCT/type: yes/0 |
| Extra: 0114e888e93f498ad8bf3e571672bbf716d81555ac30c8097d5f718c10e88a56fd020900000001e49593ff00 | ||
1 output(s) for total of 34.791777028142 HMNY
| stealth address | amount | amount idx | tag |
| 00: ae17b75895eb7b3c5de59bdacea058dab22b583ec11336d01086ecc273a438b0 | 34.791777028142 | 7343 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": 5944,
"vin": [ {
"gen": {
"height": 5884
}
}
],
"vout": [ {
"amount": 34791777028142,
"target": {
"tagged_key": {
"key": "ae17b75895eb7b3c5de59bdacea058dab22b583ec11336d01086ecc273a438b0",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 20, 232, 136, 233, 63, 73, 138, 216, 191, 62, 87, 22, 114, 187, 247, 22, 216, 21, 85, 172, 48, 200, 9, 125, 95, 113, 140, 16, 232, 138, 86, 253, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}