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: f287f599fc3bdb11d4020a3b8e90505f219f1048877950c47028131fdf195bcd
Tx prefix hash: 0d0cb3ff9331b160d87431028a8da317bd1a10e126dd12b22200759a361978fd
Tx public key: a27d23b4fb1aea71a67a029d5b224090b8f5a3cb214dd43b82e8a1714948ff04
| Timestamp: 1779771490 | Timestamp [UTC]: 2026-05-26 04:58:10 | Age [y:d:h:m:s]: 00:022:04:16:56 |
| Block: 2015 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6730 | RingCT/type: yes/0 |
| Extra: 01a27d23b4fb1aea71a67a029d5b224090b8f5a3cb214dd43b82e8a1714948ff0402090000000126697be300 | ||
1 output(s) for total of 35.055272372905 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1e12e35a0fb13f823a770b63ef9caa7c2efa15e6cd9a645dfd3a7b243cca7ce7 | 35.055272372905 | 2301 of 0 | <1b> |
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": 2075,
"vin": [ {
"gen": {
"height": 2015
}
}
],
"vout": [ {
"amount": 35055272372905,
"target": {
"tagged_key": {
"key": "1e12e35a0fb13f823a770b63ef9caa7c2efa15e6cd9a645dfd3a7b243cca7ce7",
"view_tag": "1b"
}
}
}
],
"extra": [ 1, 162, 125, 35, 180, 251, 26, 234, 113, 166, 122, 2, 157, 91, 34, 64, 144, 184, 245, 163, 203, 33, 77, 212, 59, 130, 232, 161, 113, 73, 72, 255, 4, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}