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: 96fdc37a9fdc4ad8f03d0d25cb1b802b28cab594539705669d8a44f7e5d210e9
Tx prefix hash: bc2b850a3c452755ee627cd5c83b0c7d7a91dc6d222795e8692df85fe2ee7ce0
Tx public key: 55649df6d0c0f32776b50fe13cc795fcaef3ffa9fbe827f91ceae8489ca93c55
| Timestamp: 1779479838 | Timestamp [UTC]: 2026-05-22 19:57:18 | Age [y:d:h:m:s]: 00:017:05:38:39 |
| Block: 639 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7247 | RingCT/type: yes/0 |
| Extra: 0155649df6d0c0f32776b50fe13cc795fcaef3ffa9fbe827f91ceae8489ca93c5502090000000393369e7d00 | ||
1 output(s) for total of 35.141582633183 HMNY
| stealth address | amount | amount idx | tag |
| 00: e7645be37949da9ee456c8e8c5a601fad70d9e58ec522c2afc293449893e8fcb | 35.141582633183 | 679 of 0 | <cd> |
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": 699,
"vin": [ {
"gen": {
"height": 639
}
}
],
"vout": [ {
"amount": 35141582633183,
"target": {
"tagged_key": {
"key": "e7645be37949da9ee456c8e8c5a601fad70d9e58ec522c2afc293449893e8fcb",
"view_tag": "cd"
}
}
}
],
"extra": [ 1, 85, 100, 157, 246, 208, 192, 243, 39, 118, 181, 15, 225, 60, 199, 149, 252, 174, 243, 255, 169, 251, 232, 39, 249, 28, 234, 232, 72, 156, 169, 60, 85, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}