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: c111e9138c1ac82e8fb77e1592b97d6435f098ede54fc2e5ac978f13de98c519
Tx prefix hash: 98450a9f872d61ec1403f34ca8a6bc21fae73d4cd4fc483e2fab6c1982e620b4
Tx public key: bfb9e5460c5df54aedea9564a360465f83d6f392c3ba22b7133584f34987a767
| Timestamp: 1780749996 | Timestamp [UTC]: 2026-06-06 12:46:36 | Age [y:d:h:m:s]: 00:002:12:49:21 |
| Block: 6486 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1400 | RingCT/type: yes/0 |
| Extra: 01bfb9e5460c5df54aedea9564a360465f83d6f392c3ba22b7133584f34987a767020900000008e49593ff00 | ||
1 output(s) for total of 34.751851167261 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3f80c5989bfe396b174ffffd42aaddbd3b97c13ad7a4833c28ebd9d9cabe95ec | 34.751851167261 | 7981 of 0 | <80> |
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": 6546,
"vin": [ {
"gen": {
"height": 6486
}
}
],
"vout": [ {
"amount": 34751851167261,
"target": {
"tagged_key": {
"key": "3f80c5989bfe396b174ffffd42aaddbd3b97c13ad7a4833c28ebd9d9cabe95ec",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 191, 185, 229, 70, 12, 93, 245, 74, 237, 234, 149, 100, 163, 96, 70, 95, 131, 214, 243, 146, 195, 186, 34, 183, 19, 53, 132, 243, 73, 135, 167, 103, 2, 9, 0, 0, 0, 8, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}