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: 33cae2ef9143ce5a9e9af278f09a09af1dd4cbdc6cd2f1ebf078ba47612d154f
Tx prefix hash: 8a6791513675a9ae2abb8f4c7505a2c98776d7be53ee7987627938ea5238c647
Tx public key: d8ccd6678f2c5063ef00695713d858e4bc90f4a39a2b10dc09cf5711a4e964ed
| Timestamp: 1780690041 | Timestamp [UTC]: 2026-06-05 20:07:21 | Age [y:d:h:m:s]: 00:003:03:11:32 |
| Block: 5630 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2256 | RingCT/type: yes/0 |
| Extra: 01d8ccd6678f2c5063ef00695713d858e4bc90f4a39a2b10dc09cf5711a4e964ed020900000001e49593ff00 | ||
1 output(s) for total of 34.808636580116 HMNY
| stealth address | amount | amount idx | tag |
| 00: 186480e011c26107ea1e08b6108da70cd91eaa005a1e166cb927678c2926145a | 34.808636580116 | 7077 of 0 | <a0> |
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": 5690,
"vin": [ {
"gen": {
"height": 5630
}
}
],
"vout": [ {
"amount": 34808636580116,
"target": {
"tagged_key": {
"key": "186480e011c26107ea1e08b6108da70cd91eaa005a1e166cb927678c2926145a",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 216, 204, 214, 103, 143, 44, 80, 99, 239, 0, 105, 87, 19, 216, 88, 228, 188, 144, 244, 163, 154, 43, 16, 220, 9, 207, 87, 17, 164, 233, 100, 237, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}