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: e402799f5f0c8c9a7271d5849ca17d5e6fc1c9d79f61eabe0a3eb3f709972e1c
Tx prefix hash: 904cdfcfdb0b9d55a68bab69f225867990f4b996bdde3c13411d16e80680e88d
Tx public key: 44bdbb7f3a725ae0a6a77b9491727596dca31eceb7a1d93d0908fff169361f21
| Timestamp: 1779999114 | Timestamp [UTC]: 2026-05-28 20:11:54 | Age [y:d:h:m:s]: 00:011:04:34:53 |
| Block: 4045 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3841 | RingCT/type: yes/0 |
| Extra: 0144bdbb7f3a725ae0a6a77b9491727596dca31eceb7a1d93d0908fff169361f2102090000000226697be300 | ||
1 output(s) for total of 34.916644752133 HMNY
| stealth address | amount | amount idx | tag |
| 00: a6b835f46e46e557ee29917dc4e9984bf2ddb70bc2008e201a014faab11b346c | 34.916644752133 | 5008 of 0 | <18> |
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": 4105,
"vin": [ {
"gen": {
"height": 4045
}
}
],
"vout": [ {
"amount": 34916644752133,
"target": {
"tagged_key": {
"key": "a6b835f46e46e557ee29917dc4e9984bf2ddb70bc2008e201a014faab11b346c",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 68, 189, 187, 127, 58, 114, 90, 224, 166, 167, 123, 148, 145, 114, 117, 150, 220, 163, 30, 206, 183, 161, 217, 61, 9, 8, 255, 241, 105, 54, 31, 33, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}