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: c14bd02fb0591ee2c2ab8aa067206852b390c643f6b2b3d5e12c5131aa5bd27a
Tx prefix hash: dd169e6362f740ba86c629bf1c08f66f607b24b569c9653a6681584891a191dd
Tx public key: d0c726a4abc744d8482e323b6b8ca36feb3f5b6967d1b931baf28eea1d6476ab
| Timestamp: 1779735147 | Timestamp [UTC]: 2026-05-25 18:52:27 | Age [y:d:h:m:s]: 00:014:05:54:20 |
| Block: 1912 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5974 | RingCT/type: yes/0 |
| Extra: 01d0c726a4abc744d8482e323b6b8ca36feb3f5b6967d1b931baf28eea1d6476ab02090000000626697be300 | ||
1 output(s) for total of 35.058971567215 HMNY
| stealth address | amount | amount idx | tag |
| 00: dbaf3c621c97350c70d594f103ac20fec2ebf8bfa0d372549f0c5ee5a0150fc4 | 35.058971567215 | 2142 of 0 | <34> |
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": 1972,
"vin": [ {
"gen": {
"height": 1912
}
}
],
"vout": [ {
"amount": 35058971567215,
"target": {
"tagged_key": {
"key": "dbaf3c621c97350c70d594f103ac20fec2ebf8bfa0d372549f0c5ee5a0150fc4",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 208, 199, 38, 164, 171, 199, 68, 216, 72, 46, 50, 59, 107, 140, 163, 111, 235, 63, 91, 105, 103, 209, 185, 49, 186, 242, 142, 234, 29, 100, 118, 171, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}