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: 299e83cf567e8568ce06f6c95b489044ac59ac626bd2af14bff2193a2f0984a1
Tx prefix hash: 6cc9aeaf25b6dab8201a59f2703c670ca11479a69cc53e834520476042c0a4e1
Tx public key: 931542730077eef2639556f44def4928e94d812ed6f3d2f1c8d3a1a2f367662d
| Timestamp: 1780731399 | Timestamp [UTC]: 2026-06-06 07:36:39 | Age [y:d:h:m:s]: 00:002:19:03:57 |
| Block: 6321 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1576 | RingCT/type: yes/0 |
| Extra: 01931542730077eef2639556f44def4928e94d812ed6f3d2f1c8d3a1a2f367662d020900000002e49593ff00 | ||
1 output(s) for total of 34.762789741664 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0bdabc864c59ba7a7d2d552a5120702b020e32cc557217a00b507cd62d9cc259 | 34.762789741664 | 7806 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": 6381,
"vin": [ {
"gen": {
"height": 6321
}
}
],
"vout": [ {
"amount": 34762789741664,
"target": {
"tagged_key": {
"key": "0bdabc864c59ba7a7d2d552a5120702b020e32cc557217a00b507cd62d9cc259",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 147, 21, 66, 115, 0, 119, 238, 242, 99, 149, 86, 244, 77, 239, 73, 40, 233, 77, 129, 46, 214, 243, 210, 241, 200, 211, 161, 162, 243, 103, 102, 45, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}