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: 89f2449e124aab61d03995236847e0996c52613708f128e290d188bde45c848a
Tx prefix hash: 8dee7f101af7665975cbd4f234165ac293470771cc503c2ab618d9f932ae97a6
Tx public key: 549d84aeaa3f82d43cbaf032abe26d40488f1cddca66324a4ae6ca4b07d8f58b
| Timestamp: 1780689772 | Timestamp [UTC]: 2026-06-05 20:02:52 | Age [y:d:h:m:s]: 00:003:07:48:06 |
| Block: 5620 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2331 | RingCT/type: yes/0 |
| Extra: 01549d84aeaa3f82d43cbaf032abe26d40488f1cddca66324a4ae6ca4b07d8f58b020900000001e49593ff00 | ||
1 output(s) for total of 34.809300509135 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7fce005a42be4693ab9cc574868ece5f650a4ebe2706e5d92b8cac03c4c07a88 | 34.809300509135 | 7067 of 0 | <d5> |
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": 5680,
"vin": [ {
"gen": {
"height": 5620
}
}
],
"vout": [ {
"amount": 34809300509135,
"target": {
"tagged_key": {
"key": "7fce005a42be4693ab9cc574868ece5f650a4ebe2706e5d92b8cac03c4c07a88",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 84, 157, 132, 174, 170, 63, 130, 212, 60, 186, 240, 50, 171, 226, 109, 64, 72, 143, 28, 221, 202, 102, 50, 74, 74, 230, 202, 75, 7, 216, 245, 139, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}