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: 4f5def70bc8592849f83fdacddb1f4174864509df3679573b501ac9609f1bac0
Tx prefix hash: a7e9f9bceee1edfd96f019dfed1d284dac27e8c2ec33f4e79b9ee62ac9b5fded
Tx public key: 43ab94523b0ac64b5b548791b7ea6a10b9c29c4c60ed106c06f9715b66df3462
| Timestamp: 1780043901 | Timestamp [UTC]: 2026-05-29 08:38:21 | Age [y:d:h:m:s]: 00:010:16:57:36 |
| Block: 4321 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3565 | RingCT/type: yes/0 |
| Extra: 0143ab94523b0ac64b5b548791b7ea6a10b9c29c4c60ed106c06f9715b66df346202090000000126697be300 | ||
1 output(s) for total of 34.900671042099 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6c7f68fb24ea17509ba95b1c62e48c054e1fa85172616c47b575d2989c508b60 | 34.900671042099 | 5399 of 0 | <f8> |
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": 4381,
"vin": [ {
"gen": {
"height": 4321
}
}
],
"vout": [ {
"amount": 34900671042099,
"target": {
"tagged_key": {
"key": "6c7f68fb24ea17509ba95b1c62e48c054e1fa85172616c47b575d2989c508b60",
"view_tag": "f8"
}
}
}
],
"extra": [ 1, 67, 171, 148, 82, 59, 10, 198, 75, 91, 84, 135, 145, 183, 234, 106, 16, 185, 194, 156, 76, 96, 237, 16, 108, 6, 249, 113, 91, 102, 223, 52, 98, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}