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: 43f84013783f2f0e74b3e3dd22cdf73313430be8585936d1f993fdd86214fe7e
Tx prefix hash: 4ddc020d0470af666bf48789eaab4c71b24b9d14b3366bf9b1151127842520bb
Tx public key: 064f27fbe4425c9e55b6783ea2eda1781ba820df59167e5331bf25792349b968
| Timestamp: 1780782602 | Timestamp [UTC]: 2026-06-06 21:50:02 | Age [y:d:h:m:s]: 00:002:06:43:00 |
| Block: 6779 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1251 | RingCT/type: yes/0 |
| Extra: 01064f27fbe4425c9e55b6783ea2eda1781ba820df59167e5331bf25792349b968020900000002e49593ff00 | ||
1 output(s) for total of 34.732435393060 HMNY
| stealth address | amount | amount idx | tag |
| 00: ce9a0feb69c5a420c093b3a878087f3e6bd3ae720c1ac6df348a9561838ed5ea | 34.732435393060 | 8371 of 0 | <28> |
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": 6839,
"vin": [ {
"gen": {
"height": 6779
}
}
],
"vout": [ {
"amount": 34732435393060,
"target": {
"tagged_key": {
"key": "ce9a0feb69c5a420c093b3a878087f3e6bd3ae720c1ac6df348a9561838ed5ea",
"view_tag": "28"
}
}
}
],
"extra": [ 1, 6, 79, 39, 251, 228, 66, 92, 158, 85, 182, 120, 62, 162, 237, 161, 120, 27, 168, 32, 223, 89, 22, 126, 83, 49, 191, 37, 121, 35, 73, 185, 104, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}