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: 1cb0b3b46f0892244e4fe3b6b154ea1c9e1495f230dccc45d4ca99b9e7d79ece
Tx prefix hash: 6927eb65d61f022280b748a27e231eaec6899e9eac0a03eb6e010b1b3ff320fd
Tx public key: 0d6b46c4cd0261042c225640806a6998b21fd5951aa1f9e2540de0663dd60cef
| Timestamp: 1779872706 | Timestamp [UTC]: 2026-05-27 09:05:06 | Age [y:d:h:m:s]: 00:012:17:35:30 |
| Block: 2836 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5060 | RingCT/type: yes/0 |
| Extra: 010d6b46c4cd0261042c225640806a6998b21fd5951aa1f9e2540de0663dd60cef02090000000226697be300 | ||
1 output(s) for total of 34.994631735549 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2e9256e3829c5dccf711098cd28410491c271ef307ed41f54e3d0dad8c843af8 | 34.994631735549 | 3356 of 0 | <4b> |
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": 2896,
"vin": [ {
"gen": {
"height": 2836
}
}
],
"vout": [ {
"amount": 34994631735549,
"target": {
"tagged_key": {
"key": "2e9256e3829c5dccf711098cd28410491c271ef307ed41f54e3d0dad8c843af8",
"view_tag": "4b"
}
}
}
],
"extra": [ 1, 13, 107, 70, 196, 205, 2, 97, 4, 44, 34, 86, 64, 128, 106, 105, 152, 178, 31, 213, 149, 26, 161, 249, 226, 84, 13, 224, 102, 61, 214, 12, 239, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}