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: 9e138fdf845f80fde35430a6a4e2c0c6acd215f2af6f36405c4a53c25a4aa26f
Tx prefix hash: b15f8e99a8e6b237d4c05bcedb7d6be059d3a89ac2becf80a8ffb12efcc38674
Tx public key: 41239ab3af90b097f730300678badd8d8cd5214a10c8d8ca28cf8c7c36932692
| Timestamp: 1780761238 | Timestamp [UTC]: 2026-06-06 15:53:58 | Age [y:d:h:m:s]: 00:002:08:52:49 |
| Block: 6568 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1318 | RingCT/type: yes/0 |
| Extra: 0141239ab3af90b097f730300678badd8d8cd5214a10c8d8ca28cf8c7c36932692020900000001e49593ff00 | ||
1 output(s) for total of 34.746416307645 HMNY
| stealth address | amount | amount idx | tag |
| 00: 064ec61fcba66be63c932db21db900a974e1c7c80d33c1477dbe99a139f71641 | 34.746416307645 | 8090 of 0 | <a5> |
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": 6628,
"vin": [ {
"gen": {
"height": 6568
}
}
],
"vout": [ {
"amount": 34746416307645,
"target": {
"tagged_key": {
"key": "064ec61fcba66be63c932db21db900a974e1c7c80d33c1477dbe99a139f71641",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 65, 35, 154, 179, 175, 144, 176, 151, 247, 48, 48, 6, 120, 186, 221, 141, 140, 213, 33, 74, 16, 200, 216, 202, 40, 207, 140, 124, 54, 147, 38, 146, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}