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: 2a34f24f38f7aad60fa7859e13ba0b8664ed70ba55c89d3a383518c61f9fda48
Tx prefix hash: 8f670d1da0f1f91fc4fd1e073dd07dc5d245edd77731a97a1c5a5758bc4bef78
Tx public key: 7240ab41107336a1d485267c9c1ce16d43fb25148f01702b490516f10d8d0997
| Timestamp: 1780698310 | Timestamp [UTC]: 2026-06-05 22:25:10 | Age [y:d:h:m:s]: 00:003:03:10:47 |
| Block: 6022 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1864 | RingCT/type: yes/0 |
| Extra: 017240ab41107336a1d485267c9c1ce16d43fb25148f01702b490516f10d8d0997020900000001e49593ff00 | ||
1 output(s) for total of 34.782620537850 HMNY
| stealth address | amount | amount idx | tag |
| 00: 633a325dd64c39f12d10c200e8b9d5c90c46386bc52549419446b9dfe7fbfb86 | 34.782620537850 | 7489 of 0 | <ef> |
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": 6082,
"vin": [ {
"gen": {
"height": 6022
}
}
],
"vout": [ {
"amount": 34782620537850,
"target": {
"tagged_key": {
"key": "633a325dd64c39f12d10c200e8b9d5c90c46386bc52549419446b9dfe7fbfb86",
"view_tag": "ef"
}
}
}
],
"extra": [ 1, 114, 64, 171, 65, 16, 115, 54, 161, 212, 133, 38, 124, 156, 28, 225, 109, 67, 251, 37, 20, 143, 1, 112, 43, 73, 5, 22, 241, 13, 141, 9, 151, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}