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: a1afd4d5eb662a7d72b1b9a1331b8d4009b907ef9502dab7dcabc2dab0bb6461
Tx prefix hash: 66edd7d7ab9fbb94e633c319255f070fd44243559b40b8771d55b11808c64d95
Tx public key: c0b0cd0519171646806043b71f4ca40c64486d8077a09f205df329efd1a1ccd9
| Timestamp: 1780820178 | Timestamp [UTC]: 2026-06-07 08:16:18 | Age [y:d:h:m:s]: 00:002:08:52:45 |
| Block: 7156 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1578 | RingCT/type: yes/0 |
| Extra: 01c0b0cd0519171646806043b71f4ca40c64486d8077a09f205df329efd1a1ccd9020900000001e49593ff00 | ||
1 output(s) for total of 34.707469279112 HMNY
| stealth address | amount | amount idx | tag |
| 00: 963002defc4f7e62e5e7b10016c1b2fa9d00f6cd270d987de83a8534a552470b | 34.707469279112 | 8816 of 0 | <82> |
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": 7216,
"vin": [ {
"gen": {
"height": 7156
}
}
],
"vout": [ {
"amount": 34707469279112,
"target": {
"tagged_key": {
"key": "963002defc4f7e62e5e7b10016c1b2fa9d00f6cd270d987de83a8534a552470b",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 192, 176, 205, 5, 25, 23, 22, 70, 128, 96, 67, 183, 31, 76, 164, 12, 100, 72, 109, 128, 119, 160, 159, 32, 93, 243, 41, 239, 209, 161, 204, 217, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}