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: 177e089f1d6101c62d29b4956fd8f63b133dcf879f9e4e5dfc949e8a242d100e
Tx prefix hash: 8565ee721c3107d105560156059f174a8fbaea84515c3158ca4ef242bb6e66a7
Tx public key: e8a3672bf10d2e350d421c267563209a276dcba4161489046cc611478c285545
| Timestamp: 1779634348 | Timestamp [UTC]: 2026-05-24 14:52:28 | Age [y:d:h:m:s]: 00:015:10:43:29 |
| Block: 1032 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6854 | RingCT/type: yes/0 |
| Extra: 01e8a3672bf10d2e350d421c267563209a276dcba4161489046cc611478c285545020900000001ba6d17be00 | ||
1 output(s) for total of 35.115250769240 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff7310e17c1f4cfe35f73c8ace79ce9846932e62abdd28e514031ed0a2d04089 | 35.115250769240 | 1170 of 0 | <c1> |
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": 1092,
"vin": [ {
"gen": {
"height": 1032
}
}
],
"vout": [ {
"amount": 35115250769240,
"target": {
"tagged_key": {
"key": "ff7310e17c1f4cfe35f73c8ace79ce9846932e62abdd28e514031ed0a2d04089",
"view_tag": "c1"
}
}
}
],
"extra": [ 1, 232, 163, 103, 43, 241, 13, 46, 53, 13, 66, 28, 38, 117, 99, 32, 154, 39, 109, 203, 164, 22, 20, 137, 4, 108, 198, 17, 71, 140, 40, 85, 69, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}