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: 3bbac97a4fa7a5bb0f4d4b5ba2f768d6fae0d4ef5845b84fa730f3017ea437b6
Tx prefix hash: 9fcea5a7b899ab36af7f39ab9e04e59beeb2d04787579d4df886aa6914e0f1f8
Tx public key: 342d3ea280df8a0986e82ae6987ca78d4c6def90ba823ad3ccbec1f23c152ec8
| Timestamp: 1780818696 | Timestamp [UTC]: 2026-06-07 07:51:36 | Age [y:d:h:m:s]: 00:006:03:29:29 |
| Block: 7121 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1624 | RingCT/type: yes/0 |
| Extra: 01342d3ea280df8a0986e82ae6987ca78d4c6def90ba823ad3ccbec1f23c152ec8020900000001e49593ff00 | ||
1 output(s) for total of 34.709786332203 HMNY
| stealth address | amount | amount idx | tag |
| 00: de0db6d38dbab5cd7b8705d60f2b1bbb13aa0534913cb007f7a24387acb212a2 | 34.709786332203 | 8777 of 0 | <76> |
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": 7181,
"vin": [ {
"gen": {
"height": 7121
}
}
],
"vout": [ {
"amount": 34709786332203,
"target": {
"tagged_key": {
"key": "de0db6d38dbab5cd7b8705d60f2b1bbb13aa0534913cb007f7a24387acb212a2",
"view_tag": "76"
}
}
}
],
"extra": [ 1, 52, 45, 62, 162, 128, 223, 138, 9, 134, 232, 42, 230, 152, 124, 167, 141, 76, 109, 239, 144, 186, 130, 58, 211, 204, 190, 193, 242, 60, 21, 46, 200, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}